• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: matrix-project-plugin, parameterized-trigger-plugin
• Labels:

  None
• Environment:

  Jenkins 1.480.1

[JENKINS-16369] Matrix job triggers job multiple times

Alex Vesely created issue - 2013-01-16 05:52

Alex Vesely made changes - 2013-01-16 05:53

Description

Original: 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: # 115: Started by upstream project test_job/label=A build number 181 # 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

New: 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

Alex Vesely made changes - 2013-01-16 05:54

Description

Original: 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

New: 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

Alex Vesely made changes - 2013-01-16 05:54

Description

Original: 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

New: 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

Alex Vesely made changes - 2013-01-16 05:54

Description

Original: 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

New: 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

cjo9900 made changes - 2013-02-27 13:16

Assignee	Original: huybrechts [ huybrechts ]	New: cjo9900 [ cjo9900 ]
Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Jenkins IRC Bot made changes - 2014-09-27 15:29

Component/s		New: matrix-project [ 18765 ]
Component/s	Original: matrix [ 15501 ]

R. Tyler Croy made changes - 2016-07-25 23:55

Workflow

Original: JNJira [ 147187 ]

New: JNJira + In-Review [ 192268 ]