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
I don’t think there is any way of doing this. Can you explain what you are
trying to achieve?
If your idea is that Job B will reference the workspace from Job A, then in
Jenkins that’s an anti-pattern. The correct approach in that case is for Job A
to archive some artifacts, and then Job B
Yes, the idea is that I will force jobA and jobB to use the same workspace,
and run exactly the same as if they were still the same monolithic job they
were before.
Using archives doesn't really work me, as the files that would need to be
archived are spread throughout the entire workspace,
