Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
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
-
JENKINS-42511 Computed Folder API poorly designed for concurrent event processing
-
- Closed
-
- is related to
-
JENKINS-15156 Builds disappear from build history after completion
-
- Resolved
-
-
JENKINS-10709 multiple builds are triggered for one change in Gerrit
-
- Resolved
-
-
JENKINS-23130 nextBuildNumber keeps being set to previous numbers
-
- Resolved
-
-
JENKINS-25962 Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
-
- Reopened
-
-
JENKINS-27530 ISE from RunMap.put after reloading configuration from disk
-
- Resolved
-
-
JENKINS-26582 ISE from RunMap.put using /git/notifyCommit on a matrix project
-
- Closed
-
-
JENKINS-24380 Use build numbers as IDs
-
- Resolved
-
- links to
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.