Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35666

Regular 404s for running builds that get better after build is finished.

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      For some large (50%?) number of builds (across several projects):

      • The build starts.

      As expected:

      After running for several minutes:

      However:

      • the list of workers still shows the build as occupying the worker (and provides a link which goes to the now 404-ing build page)
      • the build runs to completion successfully.
      • Build-related URLs for other builds still work ok at this point.

      After the build has run to completion, all of the build related URLs which started 404ing work again (for example the complete console output can be seen).

      A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the build, not just the progressive console.

      This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this codebase/machine.

        Attachments

          Activity

          benclifford Ben Clifford created issue -
          benclifford Ben Clifford made changes -
          Field Original Value New Value
          Description For some large (50%?) number of build jobs:
           * The job starts.
           * Job related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console/job/beautilytics/branch/benc-typo/1/console provides a working progressive console.
           * The job appears in the LHS "build history" pane on the project page, as an in-progress job.
           * The job appears on the list of workers, as occupying a worker.
           * The job is correctly linked on github as an in-progress job.

          After running for several minutes, all job related URLs start returning 404, but the list of workers still shows the job as occupying the worker, and the job runs to completion successfully.

          After the job has run to completion, all of the job related URLs which started 404ing work again (for example the complete console output can be seen).

          A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the job, not just the progressive console.

          This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this project.
          For some large (50%?) number of builds (across several projects):
           * The build starts.

          As expected:
           * build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console provides a working progressive console.
           * The build appears in the LHS "build history" pane on the project page, as an in-progress build.
           * The build appears on the list of workers, as occupying a worker.
           * The build is correctly linked on github as an in-progress build.

          After running for several minutes, all build related URLs for that particular build start returning 404, but the list of workers still shows the build as occupying the worker (and provides a link which goes to the now 404-ing build page), and the build runs to completion successfully. Build-related URLs for other builds still work ok at this point.

          After the build has run to completion, all of the build related URLs which started 404ing work again (for example the complete console output can be seen).

          A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the build, not just the progressive console.

          This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this codebase/machine.
          benclifford Ben Clifford made changes -
          Summary Regular 404s for running jobs that get better after job is finished. Regular 404s for running builds that get better after build is finished.
          benclifford Ben Clifford made changes -
          Description For some large (50%?) number of builds (across several projects):
           * The build starts.

          As expected:
           * build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console provides a working progressive console.
           * The build appears in the LHS "build history" pane on the project page, as an in-progress build.
           * The build appears on the list of workers, as occupying a worker.
           * The build is correctly linked on github as an in-progress build.

          After running for several minutes, all build related URLs for that particular build start returning 404, but the list of workers still shows the build as occupying the worker (and provides a link which goes to the now 404-ing build page), and the build runs to completion successfully. Build-related URLs for other builds still work ok at this point.

          After the build has run to completion, all of the build related URLs which started 404ing work again (for example the complete console output can be seen).

          A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the build, not just the progressive console.

          This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this codebase/machine.
          For some large (50%?) number of builds (across several projects):
           * The build starts.

          As expected:
           * build related URLs work ok. (for example, http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1/console provides a working progressive console.
           * The build appears in the LHS "build history" pane on the project page, as an in-progress build.
           * The build appears on the list of workers, as occupying a worker.
           * The build is correctly linked on github as an in-progress build.

          After running for several minutes:

           * all build related URLs for that particular build start returning 404 (in the above url example, everything beginning: http://loris.beautifuldestinations.com:2000/job/beautilytics/branch/benc-typo/1)
           * and the project page ceases to show this build as existing. It displays previously finished builds.

          However:

           * the list of workers still shows the build as occupying the worker (and provides a link which goes to the now 404-ing build page)
           * the build runs to completion successfully.
           * Build-related URLs for other builds still work ok at this point.

          After the build has run to completion, all of the build related URLs which started 404ing work again (for example the complete console output can be seen).

          A screenshot of progressive console output breaking part way due to this is attached - to be clear, this happens for all URLs related to the build, not just the progressive console.

          This has happened in all of the weekly releases that I've tried (three or four over the past two months); previous to that I was not using Jenkins on this codebase/machine.
          danielbeck Daniel Beck made changes -
          Component/s freestyle-multibranch-plugin [ 20021 ]
          Component/s core [ 15593 ]
          danielbeck Daniel Beck made changes -
          Assignee Jesse Glick [ jglick ]
          danielbeck Daniel Beck made changes -
          Component/s multi-branch-project-plugin [ 21127 ]
          Component/s freestyle-multibranch-plugin [ 20021 ]
          Assignee Jesse Glick [ jglick ] Matthew DeTullio [ mjdetullio ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 172017 ] JNJira + In-Review [ 184551 ]

            People

            • Assignee:
              mjdetullio Matthew DeTullio
              Reporter:
              benclifford Ben Clifford
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: