-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Linux/tomcat - Jenkins version 1.436
If the file
configuration/jobs/<job>/nextBuildNumber
is empty, Jenkins will still initialize but the job will "disappear" from the dashboard. This will be logged, but may go unnoticed.
Oct 27, 2011 3:10:24 PM jenkins.model.Jenkins$6 onTaskFailed
SEVERE: Failed Loading job accurev_trigger
hudson.util.IOException2: <path>/configuration/jobs/<job>/nextBuildNumber doesn't contain a number
- is related to
-
JENKINS-27530 ISE from RunMap.put after reloading configuration from disk
-
- Resolved
-
I'm taking a look at this. The problem here is wether we want to
1) fix the root cause (finding out why the nextBuildNumber file is empty)
2) fixing the symptom (inserting an appropriate number in the file)
3) setting up a notification system to tell the user what happened and how to fix it.
Right now I'm taking a look at option 2) which is in theory the ugliest solution but also one that does not require user intervention