-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 1.480.1
I have a matrix job that needs to trigger another matrix job, with parameters, as soon as it starts - and then just continue with its own execution, without waiting for the 'child' to complete.
The problem is that the 'child' gets triggered several times per one 'parent' run - usually twice. The 'child' build information looks something like this:
Build 115:
Started by upstream project test_job/label=A build number 181
Build 116:
Started by upstream project test_job/label=B build number 181
Started by upstream project test_job/label=C build number 181
Started by upstream project test_job/label=D build number 181