[
https://issues.jenkins-ci.org/browse/JENKINS-11669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162321#comment-162321
]
Simon Wiest edited comment on JENKINS-11669 at 5/2/12 12:48 PM:
----------------------------------------------------------------
The issue is reproducable with Jenkins 1.461/Parameterized Trigger Plugin 2.13:
# Create a matrix job A.
# Create a freestyle job B.
# Configure a parameterized trigger in A that triggers B.
# Build A.
# The console log of the build of A shows:
{noformat}
Started by user anonymous
Triggering a new build of B #17
B #17 is already in the queue
Finished: SUCCESS
{noformat}
The reason seems to be that
{{hudson.plugins.parameterizedtrigger.BuildTrigger}} implements
{{MatrixAggregatable}} and calls {{hudson.tasks.BuildTrigger.execute}} within
the method {{endBuild}}. As triggering downstream projects is also implemented
by using the dependency graph, downstream projects are effectively triggered
twice.
The solution might be simply _not_ to implement {{MatrixAggregatable}} in
{{hudson.plugins.parameterizedtrigger.BuildTrigger}} at all, because the
dependency graph already handles the downstream project dependencies.
was (Author: swiest):
The issue is reproducable with Jenkins 1.461/Parameterized Trigger Plugin
2.13.
The reason seems to be that
{{hudson.plugins.parameterizedtrigger.BuildTrigger}} implements
{{MatrixAggregatable}} and calls {{hudson.tasks.BuildTrigger.execute}} within
the method {{endBuild}}. As triggering downstream projects is also implemented
by using the dependency graph, downstream projects are effectively triggered
twice.
The solution might be simply _not_ to implement {{MatrixAggregatable}} in
{{hudson.plugins.parameterizedtrigger.BuildTrigger}} at all, because the
dependency graph already handles the downstream project dependencies.
> 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
