Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33549

Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • core
    • None

      If $JENKINS_HOME/jobs/*/nextBuildNumber was somehow reset to a lower value then the stacktrace below will be displayed. It doesn't say what job is affected, so it might be nice to capture this exception and expose the job name.

      2016-03-10 13:03:58.785+0000 [id=4541756]   SEVERE  hudson.model.Executor#run: Unexpected executor deathjava.lang.IllegalStateException: cannot create a build with number 38 since that (or higher) is already in use among [45]
          at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
          at hudson.model.RunMap.put(RunMap.java:190)
          at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
          at hudson.model.AbstractProject.newBuild(AbstractProject.java:1010)
          at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1209)
          at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
          at hudson.model.Executor$1.call(Executor.java:335)
          at hudson.model.Executor$1.call(Executor.java:317)
          at hudson.model.Queue._withLock(Queue.java:1399)
          at hudson.model.Queue.withLock(Queue.java:1264)
          at hudson.model.Executor.run(Executor.java:317)
      

          [JENKINS-33549] Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]

          Félix Belzunce Arcos created issue -
          Félix Belzunce Arcos made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Félix Belzunce Arcos made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Yes, please expose the job name in exception.

          Claude CHOISNET added a comment - Yes, please expose the job name in exception.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 169494 ] New: JNJira + In-Review [ 185701 ]

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java
          http://jenkins-ci.org/commit/jenkins/239ec86bdb39db1009facf7eadb693d4c6c83cdd
          Log:
          Merge pull request #2125 from fbelzunc/JENKINS-33549

          [FIXED JENKINS-33549] Specify on the logger the job which cannot create a new build

          Compare: https://github.com/jenkinsci/jenkins/compare/4376fdedfc85...239ec86bdb39

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/239ec86bdb39db1009facf7eadb693d4c6c83cdd Log: Merge pull request #2125 from fbelzunc/ JENKINS-33549 [FIXED JENKINS-33549] Specify on the logger the job which cannot create a new build Compare: https://github.com/jenkinsci/jenkins/compare/4376fdedfc85...239ec86bdb39
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            fbelzunc Félix Belzunce Arcos
            fbelzunc Félix Belzunce Arcos
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: