• Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Critical Critical
    • core
    • Jenkins 1.506

      Revisiting https://issues.jenkins-ci.org/browse/JENKINS-15156 once again.

      The issue still persists. Builds are disappearing from history, even though they are present on the disk. They reappear after Jenkins restart.

        1. check_invalid_builds.sh
          3 kB
        2. check_invalid_builds.sh
          3 kB
        3. check_missing_builds.sh
          1 kB
        4. check_missing_builds.sh
          1 kB
        5. plugin1.bmp
          plugin1.bmp
          3.65 MB
        6. plugin2.bmp
          plugin2.bmp
          1.92 MB
        7. plugin3.bmp
          plugin3.bmp
          3.65 MB

          [JENKINS-17265] Builds disappearing from history

          Jesse Glick added a comment -

          @eguess74: interesting. Means RunList.iterator() is working, though that is what the main history list (HistoryWidget) should be showing too. Might not actually matter which widget is being used to search through the list—could simply be that the first iteration triggers loading of something which does not get returned until the second time.

          Really we need better diagnostics in this area. JENKINS-19400 might help.

          Jesse Glick added a comment - @eguess74: interesting. Means RunList.iterator() is working, though that is what the main history list ( HistoryWidget ) should be showing too. Might not actually matter which widget is being used to search through the list—could simply be that the first iteration triggers loading of something which does not get returned until the second time. Really we need better diagnostics in this area. JENKINS-19400 might help.

          @Jesse
          It's not about first time load as reloading history page several times after displaying the trend page with full list still produces partial result for history widget. See it here: http://s13.postimg.org/kaccjxc07/Clipboard_1.gif
          The interesting thing, however, is that history widget shows exactly "Max # of builds to keep" builds. There are more than this numbers of builds due to keep forever and trend finds them. Setting "Max # of builds to keep" to bigger value, however, doesn't make the rest of builds appear in history widget. Might be something in xml that is corrupted because of "Max # of builds to keep" coupled with lazy loading. Just a guess...

          Nikolay Martynov added a comment - @Jesse It's not about first time load as reloading history page several times after displaying the trend page with full list still produces partial result for history widget. See it here: http://s13.postimg.org/kaccjxc07/Clipboard_1.gif The interesting thing, however, is that history widget shows exactly "Max # of builds to keep" builds. There are more than this numbers of builds due to keep forever and trend finds them. Setting "Max # of builds to keep" to bigger value, however, doesn't make the rest of builds appear in history widget. Might be something in xml that is corrupted because of "Max # of builds to keep" coupled with lazy loading. Just a guess...

          iikka eklund added a comment -

          We are having exactly the same problem with Jenkins version 1.547
          This error is closed but in which Jenkins version this is fixed?

          iikka eklund added a comment - We are having exactly the same problem with Jenkins version 1.547 This error is closed but in which Jenkins version this is fixed?

          Alex Ouzounis added a comment -

          Hi all,

          I am seeing the same problem occasionally and either restarting or reloading from disk fixes the problem.

          I have a feeling that its related with:

          "WARNING: Multiple builds have the same number: "

          because every time I delete conflicting builds it goes away.

          Alex Ouzounis added a comment - Hi all, I am seeing the same problem occasionally and either restarting or reloading from disk fixes the problem. I have a feeling that its related with: "WARNING: Multiple builds have the same number: " because every time I delete conflicting builds it goes away.

          Alex Ouzounis added a comment -

          Problem no longer present in the latest versions ie 1.570

          Alex Ouzounis added a comment - Problem no longer present in the latest versions ie 1.570

          eguess74 added a comment -

          I'm seeing it happening right now on Jenkins 1.578
          I had a build that i triggered using gerrit trigger (query and trigger gerrit patches)
          It appeared in the GUI, I saw it running in the the build queue, it sent an email about build being fixed, registered the result with gerrit, but no matter how i'm trying to access it the link to the build number leads to 404. Build is present on the file system as well.

          eguess74 added a comment - I'm seeing it happening right now on Jenkins 1.578 I had a build that i triggered using gerrit trigger (query and trigger gerrit patches) It appeared in the GUI, I saw it running in the the build queue, it sent an email about build being fixed, registered the result with gerrit, but no matter how i'm trying to access it the link to the build number leads to 404. Build is present on the file system as well.

          Jesse Glick added a comment -

          eguess74 if you are using the Gerrit Trigger plugin, you are probably seeing JENKINS-23152.

          Jesse Glick added a comment - eguess74 if you are using the Gerrit Trigger plugin, you are probably seeing JENKINS-23152 .

          eguess74 added a comment -

          Jesse,

          Thanks for pointing me to the right direction!

          eguess74 added a comment - Jesse, Thanks for pointing me to the right direction!

          Frank Canova added a comment -

          I'm seeing this same issue when changing between v1.590 and v1.610. Is there a work-around or way to recreate the build.xml files? The history directories are intact but history has disappeared from the web view.

          Frank Canova added a comment - I'm seeing this same issue when changing between v1.590 and v1.610. Is there a work-around or way to recreate the build.xml files? The history directories are intact but history has disappeared from the web view.

          Daniel Beck added a comment -

          I'm seeing this same issue when changing between v1.590 and v1.610. Is there a work-around or way to recreate the build.xml files? The history directories are intact but history has disappeared from the web view.

          Unrelated issue, almost sure this is the storage layout change from http://jenkins-ci.org/changelog#v1.597 – Jenkins provides information how to downgrade the storage format in its logs, and on the UI of 1.597+. As there are 50+ watchers here, and your issue has nothing to do with this one, please move any follow-up discussion to the users mailing list or IRC.

          Daniel Beck added a comment - I'm seeing this same issue when changing between v1.590 and v1.610. Is there a work-around or way to recreate the build.xml files? The history directories are intact but history has disappeared from the web view. Unrelated issue, almost sure this is the storage layout change from http://jenkins-ci.org/changelog#v1.597 – Jenkins provides information how to downgrade the storage format in its logs, and on the UI of 1.597+. As there are 50+ watchers here, and your issue has nothing to do with this one, please move any follow-up discussion to the users mailing list or IRC.

            Unassigned Unassigned
            alex01ves Alex Vesely
            Votes:
            22 Vote for this issue
            Watchers:
            57 Start watching this issue

              Created:
              Updated:
              Resolved: