[
https://issues.jenkins-ci.org/browse/JENKINS-11669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160088#comment-160088
]
Laura Neff commented on JENKINS-11669:
--------------------------------------
I wonder if the component is correct, because I'm also seeing this from a
multi-configuration project when the downstream job is not parameterized.
I'm using Downstream-Ext plugin and in my matrix job I trigger a
non-parameterized job with Trigger for matrix projects set to ONLY_PARENT.
Should trigger just once when all configurations finish, right? But I'm seeing
two triggers in the parent log, and the job is triggered twice.
Jenkins 1.420
Downstream-Ext Plugin v. 1.6
> Parameterized trigger from a multi-configuration project triggers downstream
> jobs twice
> ---------------------------------------------------------------------------------------
>
> Key: JENKINS-11669
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11669
> Project: Jenkins
> Issue Type: Bug
> Components: parameterized-trigger
> Environment: Parameterized Trigger Plugin 2.11
> Reporter: Davi Arnaut
> Assignee: huybrechts
>
> An upstream multi-configuration project with a parameterized trigger
> schedules the downstream project twice.
> Log output from a multi-configuration job with two parameterized triggers
> (unit_test and test_suite,test_suite-valgrind):
> Triggering a new build of test_suite #21
> Triggering a new build of test_suite-valgrind #14
> Triggering a new build of unit_test #26
> Triggering a new build of test_suite #22
> Triggering a new build of test_suite-valgrind #15
> Triggering a new build of unit_test #27
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
