One way to do this is using the Priority Sorter Plugin, and give jobB a
high priority.
On 7/20/2015 10:38 AM, Porter Bassett wrote:
I am trying to break up a job into two smaller jobs, which I'll call
jobA and jobB.
I want jobB to run *immediately* after jobA, and on the same node,
just like they did when they were the same job.
I can use use the Parameterized Trigger plugin to make jobA trigger
jobB on the same node.
However, this triggering of jobB doesn't force it to run immediately.
If there are other jobs in the queue, then jobB will just be put on
the end of the queue.
How can I force jobB to always run immediately after jobA, and on the
same node?
--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com
<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/a02c83b4-0c1c-412d-83a2-006e8f57384d%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/a02c83b4-0c1c-412d-83a2-006e8f57384d%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/55AE784F.3080004%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.
