|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
> "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting.
I'm not quite a sure I know what you mean.
"Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue.
Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C.
If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here.
> Jenkins schedules a build of D because nothing says it cannot.
"Block on upstream builds" says it cannot.
D cannot be executed until any pending upstream builds (C) have finished.