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.
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Kohsuke Kawaguchi [ kohsuke ]|
|Workflow||JNJira [ 149596 ]||JNJira + In-Review [ 193202 ]|