Repository navigation
[JENKINS-11563] Jenkins should fail initialization if it can not parse a job history #16200
Description
If the file
configuration/jobs//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: /configuration/jobs//nextBuildNumber doesn't contain a number
Originally reported by 
pickgr1, imported from: Jenkins should fail initialization if it can not parse a job history
- status: Resolved
- priority: Major
- component(s): core
- resolution: Fixed
- resolved: 2011-11-02T18:16:50+00:00
- votes: 0
- watchers: 2
- imported: 2025-11-24
Raw content of original issue
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
- environment:
Linux/tomcat - Jenkins version 1.436
Activity
jenkins-infra-bot commentedon Nov 2, 2011
emanuelez:
Raw content of original comment:
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
jenkins-infra-bot commentedon Nov 2, 2011
emanuelez:
Raw content of original comment:
My fix is here: #303
jenkins-infra-bot commentedon Nov 2, 2011
Raw content of original comment:
Code changed in jenkins
User: Emanuele Zattin
Path:
changelog.html
core/src/main/java/hudson/model/Job.java
http://jenkins-ci.org/commit/jenkins/8affa6d912f2f0777487990f2d7ef2813a19b04c
Log:
[FIXED JENKINS-11563]
It would be better to find out why the nextBuildNumber is at times empty.
In the mean time this will find the appropriate number and write it to the file.
Compare: 3fb9bdb...8affa6d
jenkins-infra-bot commentedon Nov 2, 2011
Raw content of original comment:
Given that the write to the nextBuildNumber is protected in the atomic write, I'm not sure how it can be empty, but I'm merging pull #303 anyway as a defensive measure.
jenkins-infra-bot commentedon Nov 2, 2011
Raw content of original comment:
When we've seen this happen, it's usually due to some catastrophic event where the hard drive has crashed or the server that Jenkins was running on was not gracefully shutdown (power-outage). It's happened enough times though that I think this will be a very beneficial improvement for us. Thanks!
jenkins-infra-bot commentedon Nov 2, 2011
Raw content of original comment:
Integrated in
jenkins_main_trunk #1262
[FIXED JENKINS-11563]
Kohsuke Kawaguchi : 8affa6d912f2f0777487990f2d7ef2813a19b04c
Files :
jenkins-infra-bot commentedon Nov 24, 2025
[Original
relates_tofrom Jira: JENKINS-27530]