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

          I suggest logging that as a new issue and linking it to this one. Irrespective of whether or not it is related the comments trail/information is just too big/complex on this issue.

          Richard Mortimer added a comment - I suggest logging that as a new issue and linking it to this one. Irrespective of whether or not it is related the comments trail/information is just too big/complex on this issue.

          Many issues could have similar symptoms. The root cause of the original issue has been fixed. Please log any further occurrences in a new issue.

          Richard Mortimer added a comment - Many issues could have similar symptoms. The root cause of the original issue has been fixed. Please log any further occurrences in a new issue.

          Andreas W added a comment -

          This bug is really annoying. I don't know what the root cause was here and how many bugs have the same symptom. It also happens again in Jenkins 1.570 and 1.571 on Windows Server 2008. Build occur after random time they disappear, symbolic links go away but builds are on disk...

          Andreas W added a comment - This bug is really annoying. I don't know what the root cause was here and how many bugs have the same symptom. It also happens again in Jenkins 1.570 and 1.571 on Windows Server 2008. Build occur after random time they disappear, symbolic links go away but builds are on disk...

          Similar symptoms of "disappearing builds", but different root cause.

          Konstantin Veretennicov added a comment - Similar symptoms of "disappearing builds", but different root cause.

          Code changed in jenkins
          User: Jesse Glick
          Path:
          test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
          http://jenkins-ci.org/commit/jenkins/389a565de417170f586830ee9fa7a7ec9749fc68
          Log:
          JENKINS-10615 AbstractProjectTest.testWorkspaceLock frequently fails on jenkins.ci due to InterruptedException in HudsonTestCase.setUp.
          Possibly because it is sorted after JENKINS-15156 testGetBuildAfterGC and the test suite times out.

          (cherry picked from commit 85e9e126773c0bb20a8529a2e6591dde17d7e209)

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/389a565de417170f586830ee9fa7a7ec9749fc68 Log: JENKINS-10615 AbstractProjectTest.testWorkspaceLock frequently fails on jenkins.ci due to InterruptedException in HudsonTestCase.setUp. Possibly because it is sorted after JENKINS-15156 testGetBuildAfterGC and the test suite times out. (cherry picked from commit 85e9e126773c0bb20a8529a2e6591dde17d7e209)

          Andy Shah added a comment - - edited

          Recently upgraded from Jenkins 1.540 to latest release 1.605, After upgrade noticed build history for all the Jenkins jobs were gone. I currently have close to 350 jobs and losing history is really pain. Had to downgrade to 1.540 to restore the environment.

          Update: Tried "Reload Configuration" option but no luck.

          Andy Shah added a comment - - edited Recently upgraded from Jenkins 1.540 to latest release 1.605, After upgrade noticed build history for all the Jenkins jobs were gone. I currently have close to 350 jobs and losing history is really pain. Had to downgrade to 1.540 to restore the environment. Update: Tried "Reload Configuration" option but no luck.

          Daniel Beck added a comment -

          After upgrade noticed build history for all the Jenkins jobs were gone

          Completely unrelated issue.

          Daniel Beck added a comment - After upgrade noticed build history for all the Jenkins jobs were gone Completely unrelated issue.

          ang chang added a comment -

          Hi,
          I am facing the same problem on Jenkins 1.555 on windows. Sometime build history item will disappear when running and leave the job unfinished.
          So I am wondering this bug is fixed on which version? Can I avoid this problem by upgrading to new version?

          ang chang added a comment - Hi, I am facing the same problem on Jenkins 1.555 on windows. Sometime build history item will disappear when running and leave the job unfinished. So I am wondering this bug is fixed on which version? Can I avoid this problem by upgrading to new version?

          Code changed in jenkins
          User: Johno Crawford
          Path:
          test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
          http://jenkins-ci.org/commit/jenkins-test-harness/6856f5db18f4295043438e4018e95bd454bdd0ca
          Log:
          JENKINS-15156 Refactored fix.

          Originally-Committed-As: fe95fc53f891542e63e24a64c0b7add60ac91c64

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Johno Crawford Path: test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java http://jenkins-ci.org/commit/jenkins-test-harness/6856f5db18f4295043438e4018e95bd454bdd0ca Log: JENKINS-15156 Refactored fix. Originally-Committed-As: fe95fc53f891542e63e24a64c0b7add60ac91c64

          Code changed in jenkins
          User: Jesse Glick
          Path:
          test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
          http://jenkins-ci.org/commit/jenkins-test-harness/9933530be8674c316f6be0fafc71c9239c0755f7
          Log:
          JENKINS-15156 Class loading errors can result from OOME if you are not careful.
          Originally-Committed-As: 74e6409a06531144316f2e36bdc0b069de52b94d

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java http://jenkins-ci.org/commit/jenkins-test-harness/9933530be8674c316f6be0fafc71c9239c0755f7 Log: JENKINS-15156 Class loading errors can result from OOME if you are not careful. Originally-Committed-As: 74e6409a06531144316f2e36bdc0b069de52b94d

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

              Created:
              Updated:
              Resolved: