|
||||||||
|
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.
My current theory is that either:
1) The list-of-builds is being modified by something
2) A new list-of-builds is being created at certain times (e.g. "Reload Configuration from Disk") and some things are still using the old list-of-builds. This causes the weird mis-match and possibly explains how nextBuildNumber gets "reset" to an older version. Possibly the object that is recreated is the Project itself (which holds the nextBuildNumber).
I think #2 is the more likely.