|
||||||||
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/groups/opt_out.
I have also seen this:
Running Jenkins ver. 1.466.10.1 (Jenkins Enterprise by CloudBees 12.11)
Two builds of different upstream jobs report triggering the same build # of a downstream job.
tail of UPSTREAM1 build #48 console log:
...
Sending email for trigger: Success
Sending email to: ...
Triggering a new build of DOWNSTREAM1 #157
Triggering a new build of DOWNSTREAM2 #16298
Finished: SUCCESS
tail of UPSTREAM2 build #21 console log:
...
Sending email to: ap...@amazon.com
Triggering a new build of DOWNSTREAM1 #157
Triggering a new build of DOWNSTREAM2 #16293
Finished: SUCCESS
head of DOWNSTREAM1 build #157 console log:
Started by upstream project "UPSTREAM2" build number 21
head of DOWNSTREAM1 build #160 console log:
Started by upstream project "UPSTREAM2" build number 48