|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Ordering of the dependencies when triggering downstream is done in the Build trigger (part of core not parametrised trigger plugin)
And as such does not treat any Downstream job in preference to another unless multiple downstream jobs are also linked, so that a which are triggered by multiple jobs run later.
i.e. A triggers B and C
B triggers C
In this case A would trigger B first as C could be triggered from B also.
See code @
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/BuildTrigger.java#L199
If you want jobs to run in priority order i.e. C first then B, have a look at the Priority Sorter Plugin which can cause jobs to run in a preference order when there is limited executors.
https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin
Closing this as this is not a bug
and is core functionality that expects all jobs to be equal.