Title: Message Title
Martin Ba commented on JENKINS-2002
Re: Post-build Actions Build Other Projects order is not maintained
Workaround: We use the PrioritySorter plugin anyway to sort our jobs, so we actually want then to be started in priority order (which you also can do dynamically with the BuildPriority parameter. This bug here prevents the starting in priority order, because jobs are run before all parallel downstream jobs are fully pushed into the queue. What I did was to set a global Quiet Period of 5 sec in the Jenkins Options, so that each and every job (unless otherwise specified(a)) will stay in the Queue for 5 sec - this is enough time so that all parallel downstream jobs get pushed into the queue together, therefore allowing the PrioritySorter Plugin to sort them accordingly. (a): Neat thing is the GUI buttons will add a delay=0sec, so that starting the inital job won't have any delay. If you have URL triggers, you can also spec. the delay there if the 5sec is hurting.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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/d/optout.
