-
Improvement
-
Resolution: Fixed
-
Major
The fix of JENKINS-15652 merely downgrades the error but does not clean up build records. It would make sense to have the code detect anomalous conditions and initiate a builds folder cleanup. Take only the last build of a given number, and discard any earlier with higher number. I.e. just set <number> to 0 or something and ignore such builds, or rename build.xml to build-broken.xml.
- is related to
-
JENKINS-15652 ArrayIndexOutOfBoundsException from AbstractLazyLoadRunMap.search
- Resolved
-
JENKINS-8754 ROADMAP: Improve Start-up Time
- Closed
-
JENKINS-16060 All executors crashes and are labeled DEAD (!)
- Resolved
-
JENKINS-29060 Jenkins incorrectly reports timestamps are inconsistent
- Resolved
-
JENKINS-20730 Wrong log message for out-of-order build record repair
- Resolved