-
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
-
[JENKINS-18289] Detect & repair out-of-order build records
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | New: Kohsuke Kawaguchi [ kohsuke ] |
Labels | Original: robustness | New: lazy-loading robustness |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 149596 ] | New: JNJira + In-Review [ 193202 ] |