|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
When called as a publisher of a job, ParameterrizedTrigger launches downstream jobs by registering them to DependencyGraph.
When called in a promotion, ParameterrizedTrigger launches downstream jobs by itself.
This difference seems make downstram builds lose their upstram build.
In the promotion process, PromotedBuild doesn't trigger DependencyGraph. It is the reason ParameterrizedTrigger launches downstream jobs by itself. It is mentioned in the comment in hudson.plugins.parameterizedtrigger.BuildTrigger.canDeclare, and seems reported in Hudson-5679.
(I could not access that page, however...)
On the other hand, used hudson.tasks.BuildTrigger, the upstream build can be tracked from downstram builds even called in the promotion process.
This is for PromotedBuilds treats hudson.tasks.BuildTrigger in a special way. This is done in
JENKINS-1765(and HUDSON-1765), patched in 88920e3.There could be two ways to improve ParameterrizedTrigger with PromotedBuilds.
The latter one is better as a design, but I'm not sure ParameterrizedTrigger can retrieve the original build of the promotion.