-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Platform: All, OS: All
If you create a job through the web UI, the first build is #1. If you post
config.xml to /createItem?name=..., the first build is #0.
Debugger confirms that when Job.onLoad is run, nextBuildNumber==0, despite
protected transient volatile int nextBuildNumber = 1;
Some XStream magic I suppose.
Code changed in hudson
User: : jglick
Path:
trunk/hudson/main/core/src/main/java/hudson/model/Job.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=16593
Log:
[FIXED JENKINS-3361] Programmatically created jobs started builds at #0 rather than #1.