-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 1.554.1
GerritTrigger 2.11.1
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.
- 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
[JENKINS-23152] builds getting lost due to GerritTrigger
Remote Link | New: This issue links to "May 21st IRC chat log (Web Link)" [ 10901 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Summary of the IRC chat:
On IRC schristou said that he tracked this down to GerritTrigger...
Specifically, his steps to reproduce are to "Reload Configuration from Disk" and then kick off a Gerrit build.
The nextBuildNumber was new to GerritTrigger author rsandell; "It could have something to do with cancel previous patchsets, but I'm just guessing".
I'm also fairly certain its happening to us even without "Reload Configuration from Disk" because we normally don't use that (we've been using Jenkins since the days when build info would be lost and are afraid of it).
rsandell mentioned that core not sending a start/stop signal to the triggers when a reload from disk is performed makes it very hard for him to make GerritTrigger behave better.