|
||||||||
|
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.
I'm not sure what documentation you're reading (appears to be perhaps the "?" pop-up) The checkbox under the "Advanced Projects Option" says "Block build when upstream project is building". I would suggest that if to block also if queued, then the regular text by the text box should say "Block build when upstream project is building or queued".
Second, this is not the way that it worked in 1.530 as I have numerous time when multiple jobs in a stream are queued and one does start running. So when was the implementation changed to also block on queuing? why?
Third, perhaps there are useful scenarios to block if simply queued (but none come to mind for my immediate usage).
Fourth, OK, if this check box if not the way, how can I simply block on building and not worry about if multiple jobs are queued?
My scenario is Job A builds and also produces stuff (e.g., headers) used by Job B. Job B builds. Job C deploys that artifacts. So I can't have any running at the same time (e.g., if B runs while A running, B may fail as A may not have yet produced needed items – or worse, might change needed items partway thru B's build). If the checkbox is not the way, what is the way?