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
oglegroups.com [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Porter Bassett
> *Sent:* 20 July 2015 15:39
> *To:* jenkins...@googlegroups.com
> *Subject:* Forcing another job to run immediately on same node
>
>
>
> I am trying to break up a job into two smaller
: jenkinsci-users@googlegroups.com
Subject: Forcing another job to run immediately on same node
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 jo
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.
How
