Forcing another job to run immediately on same node

[Porter Bassett]

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?

[Matthew...@diamond.ac.uk]

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 retrieve them.

 

You can make job B run on the same node as job A, but only if both jobs are tied to exactly one node, which is presumably not what you wanted.

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 

[Porter Bassett]

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, which is too big (30 GB +) to archive and retrieve in a timely manner.

And yes, you are correct that I don't want to tie jobA and jobB to only one node. 

Can you explain a little more what you mean by an anti-pattern?

[Eric Pyle]

One way to do this is using the Priority Sorter Plugin, and give jobB a high priority.

--
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-use...@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.
For more options, visit https://groups.google.com/d/optout.