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

builds getting lost due to GerritTrigger

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • gerrit-trigger-plugin
    • None
    • Jenkins 1.554.1
      GerritTrigger 2.11.1

    Description

      When viewing jobs, newer builds disappear from the build history list. Trying to go to the URL of a newer build results in a 404. The missing builds are located on disk and restarting Jenkins will make them reappear.

      Sometimes, the nextBuildNumber is set to a lower number and duplicate builds are created; two date-directories are created in builds/ but only the latest build has a build_number symlink.

      I wrote tool to help detect these problems on disk and even repair them (for some value of repair): https://github.com/docwhat/jenkins-job-checker

      A lot of history is on JENKINS-15156; I'll repeat some of it below.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-42511 Computed Folder API poorly designed for concurrent event processing

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-10709 multiple builds are triggered for one change in Gerrit

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-23130 nextBuildNumber keeps being set to previous numbers

          • Major - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-25962 Using Jenkins Job Builder to create triggers based on comment regex fails to trigger

          • Major - Major loss of function.
          • Reopened

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27530 ISE from RunMap.put after reloading configuration from disk

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

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-26582 ISE from RunMap.put using /git/notifyCommit on a matrix project

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. JENKINS-24380 Use build numbers as IDs

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link May 21st IRC chat log

          Activity

            Ascending order - Click to sort in descending order
            View 30 older comments
            batmat Baptiste Mathus added a comment - - edited

            FWIW, same or similar issue seen here too on Jenkins 1.593 (+Jenkins Gerrit plugin 2.12.0 and a 2.8.3 Gerrit server). It seems to have happened since we used reload from disk (which we do only few times a year) and only affects Gerrit builds.
            Even when triggered manually with the "query & trigger Gerrit Patches", we see the new build displayed on the left of the screen. But it does not appear in the job page and leads to a 404 when accessed. And the build is indeed on the disk and seems to run just fine. So more something like a GUI issue.

            Will post more informations here if we manage to reproduce the issue non randomly.

            batmat Baptiste Mathus added a comment - - edited FWIW, same or similar issue seen here too on Jenkins 1.593 (+Jenkins Gerrit plugin 2.12.0 and a 2.8.3 Gerrit server). It seems to have happened since we used reload from disk (which we do only few times a year) and only affects Gerrit builds. Even when triggered manually with the "query & trigger Gerrit Patches", we see the new build displayed on the left of the screen. But it does not appear in the job page and leads to a 404 when accessed. And the build is indeed on the disk and seems to run just fine. So more something like a GUI issue. Will post more informations here if we manage to reproduce the issue non randomly.
            rsandell rsandell added a comment -

            And what happens if you upgrade to >= 2.13 where efforts have been made to fix this?

            rsandell rsandell added a comment - And what happens if you upgrade to >= 2.13 where efforts have been made to fix this?
            batmat Baptiste Mathus added a comment -

            rsandell We plan to upgrade our instance quite soon, we'll see it this comes back. Thanks for the feedback.

            batmat Baptiste Mathus added a comment - rsandell We plan to upgrade our instance quite soon, we'll see it this comes back. Thanks for the feedback.
            canoztokmak Can Oztokmak added a comment -

            upgrading gerrit plugin to 2.14.0 resolved our issue.

            canoztokmak Can Oztokmak added a comment - upgrading gerrit plugin to 2.14.0 resolved our issue.
            rsandell rsandell added a comment -

            Version 2.13.0

            rsandell rsandell added a comment - Version 2.13.0

            People

              rsandell rsandell
              docwhat Christian Höltje
              Votes:
              7 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: