|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I had posted a comment a couple of weeks ago, but it's not showing up here.
In any case I was just able to reproduce the problem today. It's been about 3 weeks since I last saw the problem. I got exactly the same thing to happen today.
Interesting to note, I was doing some configuration updates behind the scenes by editing config.xml for many jobs. Then to load the config I called out JenkinsURL/reload from my browser.
I wonder if it's picking up an old version of nextBuildNumber when the reload occurs? Some of the jobs were running when I reloaded. I wonder if nextBuildNumber only gets updated when the job completes?