|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The only suspicious thing I see in the job config is the use of the Heavy Job plugin. Is this problem at all reproducible for you? If so, does skipping use of Heavy Job fix it?
The critical diagnostic which was not mentioned here was whether nextBuildNumber existed and if so what it said. It is supposed to point to the next build number which should be created. If for some reason it failed to be updated, Jenkins would try to recreate a build with the same number. In the past this mistake would have resulted in an earlier build being silently overwritten. As of 1.597 it is caught.
The same applies to bugs like JENKINS-23152, with a different cause (objects held in memory with stale contents).