Is there any way to enable "single-job mode" for a batch deploy job, that will prevent other jobs from running until all the jobs in the batch have completed?
I have a batch job that runs 4 separate jobs sequentially. What I think I have seen is that another deploy job was able to "sneak" in between the 2nd and 3rd jobs of the batch. This outside deploy job was also in single-job mode and ended up rebooting the box. Not desired behavior at that time.
Ideally, if I am running a batch job sequentially, I want to have exclusive access to the targets until the entire batch job has run its course. Is that do-able?