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.

          [JENKINS-18289] Detect & repair out-of-order build records

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-15652 [ JENKINS-15652 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-8754 [ JENKINS-8754 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Kohsuke Kawaguchi made changes -
          Assignee New: Kohsuke Kawaguchi [ kohsuke ]
          Jesse Glick made changes -
          Labels Original: robustness New: lazy-loading robustness
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-20730 [ JENKINS-20730 ]
          evernat made changes -
          Link New: This issue is related to JENKINS-16060 [ JENKINS-16060 ]
          Kevin Phillips made changes -
          Link New: This issue is related to JENKINS-29060 [ JENKINS-29060 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 149596 ] New: JNJira + In-Review [ 193202 ]

            kohsuke Kohsuke Kawaguchi
            jglick Jesse Glick
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: