-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins server on windows 7 64. Slaves on windows 7 32/64.
I have a build which can trigger another build.
In the console, I have at the end of the log:
Triggering a new build of Build Hoops 3DX 5_x Windows Samples #1758
Triggering a new build of Supervisor Test Windows Continuous #2831
But I have not the same informations in Downstream build view.
The good informations are in the Downstream build view.
- is related to
-
JENKINS-12827 api should return the build number that was queued.
-
- Resolved
-
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: aparn@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