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

Builds disappearing from history

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Incomplete
    • Component/s: core
    • Labels:
    • Environment:
      Jenkins 1.506
    • Similar Issues:

      Description

      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.

        Attachments

        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

          Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-16845 NullPointer in getPreviousBuild

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-15156 Builds disappear from build history after completion

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-8754 ROADMAP: Improve Start-up Time

          • Major - Major loss of function.
          • Closed

            Activity

            Ascending order - Click to sort in descending order
            48 older comments
            Hide
            Permalink
            eguess74 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.

            Show
            eguess74 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.
            Hide
            Permalink
            jglick Jesse Glick added a comment -

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

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

            Jesse,

            Thanks for pointing me to the right direction!

            Show
            eguess74 eguess74 added a comment - Jesse, Thanks for pointing me to the right direction!
            Hide
            Permalink
            seaware 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.

            Show
            seaware 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.
            Hide
            Permalink
            danielbeck 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.

            Show
            danielbeck 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.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              alex01ves Alex Vesely
              Votes:
              22 Vote for this issue
              Watchers:
              58 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: