-
Bug
-
Resolution: Fixed
-
Trivial
The error message is reported if the nextBuildNumber is lower than the current build number:
hudson.model.Executor#run: Unexpected executor death java.lang.IllegalStateException: cannot create a build with number NUMBER since that (or higher) is already in use among [NUMBER]
Unfortunately this does not report the actual project which is hitting the issue, so it is difficult to determine which project(s) need to be fixed.
You can easily reproduce this problem by triggering 3 builds and manually setting the nextBuildNumber file to be 1. Triggering a new build will kill the build executor thread.
The issue is not reproducible at least on Jenkins 2.73.
Changing the nextBuildNumber is handled by Jenkins, and you get this message:
WARNING:
: improper nextBuildNumber 1 detected in hudson.model.FreeStyleProject@c4bd16a[JOB_NAME] with highest build number 4; adjustingJENKINS-27530Is there any other way to reproduce it?
Maybe this patch can help the error message to be more informative in case of unexpected executor death.
https://github.com/jenkinsci/jenkins/pull/2970