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

Builds disappear from build history after completion

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • core
    • Jenkins 1.477.2
      Master and Slaves Windows Server 2008 r2
      (Also on Jenkins 1.488 Windows Server 2008)

      We have recently noticed builds disappearing from the "Build History" listing on the project page. Developer was watching a build, waiting for it to complete and said it disappeared after it finished. Nothing was noted in any of the logs concerning that build.
      The data was still present on the disk and doing a reload from disk brought the build back. We have other automated jobs that deploy these builds based on build number, so it is pretty big issue in our environment.
      We are not able to reproduce at this point, but I still wanted to document what was happening.
      I have seen other JIRA issues that look similar, but in those jobs were disappearing after a restart, or upgrade. That is not the case for us. The build disappears after completion, success or failure.

          [JENKINS-15156] Builds disappear from build history after completion

          bbonn created issue -

          J White added a comment -

          I had this problem but after upgrading to Jenkins 1.486 all was back to normal

          J White added a comment - I had this problem but after upgrading to Jenkins 1.486 all was back to normal

          I have the same problem on Jenkins ver. 1.488. Master is Windows server 2008. History showed correctly after upgrading to 1.488, but disappeared after next build, so now the history is empty. The build is visible during job execution but disappears after completion.

          Tomas Hellberg added a comment - I have the same problem on Jenkins ver. 1.488. Master is Windows server 2008. History showed correctly after upgrading to 1.488, but disappeared after next build, so now the history is empty. The build is visible during job execution but disappears after completion.
          Tomas Hellberg made changes -
          Environment Original: Jenkins 1.477.2
          Master and Slaves Windows Server 2008 r2
          New: Jenkins 1.477.2
          Master and Slaves Windows Server 2008 r2
          (Also on Jenkins 1.488 Windows Server 2008)

          In my case, this might be related to JENKINS-13536, which causes loading of history to fail if the temp file store by the file upload plugin is removed.

          Tomas Hellberg added a comment - In my case, this might be related to JENKINS-13536 , which causes loading of history to fail if the temp file store by the file upload plugin is removed.

          My job keeps losing builds from the history all the time. An hour ago there where ten builds in the history, and now only the two most recent builds (out of a total of 175 builds) are shown.

          All the build data is still available on disk, and the history will show correctly again for a while following a restart of the master.

          Tomas Hellberg added a comment - My job keeps losing builds from the history all the time. An hour ago there where ten builds in the history, and now only the two most recent builds (out of a total of 175 builds) are shown. All the build data is still available on disk, and the history will show correctly again for a while following a restart of the master.

          12 hours later the history is back. This time without a master restart.

          Tomas Hellberg added a comment - 12 hours later the history is back. This time without a master restart.

          D C added a comment -

          I have the same problem (1.485). Builds disappear from the history. Often only the most recent build is visible.

          Attempting to access the URL of the missing builds manually (ie. append /51 to the job URL) produces a 404 Status Error (sorry, don't have exact text).

          Confirmed that "Reload configuration from disk" fixes the problem - full build history is again visible, and the build URLs can be accessed manually too.

          D C added a comment - I have the same problem (1.485). Builds disappear from the history. Often only the most recent build is visible. Attempting to access the URL of the missing builds manually (ie. append /51 to the job URL) produces a 404 Status Error (sorry, don't have exact text). Confirmed that "Reload configuration from disk" fixes the problem - full build history is again visible, and the build URLs can be accessed manually too.

          We have the same issue with 1.489. Restarting or reloading config from disk fixes this temporarily. Build history gets lost eventually after the next build. We have master/slave setup with 3 slaves executing jobs (all machines on Linux SLES)

          Christian Köberl added a comment - We have the same issue with 1.489. Restarting or reloading config from disk fixes this temporarily. Build history gets lost eventually after the next build. We have master/slave setup with 3 slaves executing jobs (all machines on Linux SLES)

          Cameron Horn added a comment -

          Notice this in particular with newly created jobs, where all build history will vanish after a build or two.

          Cameron Horn added a comment - Notice this in particular with newly created jobs, where all build history will vanish after a build or two.

            Unassigned Unassigned
            bbonn bbonn
            Votes:
            61 Vote for this issue
            Watchers:
            116 Start watching this issue

              Created:
              Updated:
              Resolved: