[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Title: Message Title Daniel Beck resolved as Duplicate Assuming this duplicates JENKINS-28926 , for which a fix will be in Jenkins 1.618 or so. Jenkins / JENKINS-28136 Won't run either job when both queued in an upstream/downstream situation Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck updated JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Change By: Daniel Beck (29/Apr/15 11:14 AM) Component/s: core Component/s: other Component/s: build-blocker-plugin 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck commented on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Note that the options are documented as (emphasis mine): When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. So this appears to behave as designed. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck edited a comment on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation Note that the options are documented as (emphasis mine): When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. When this option is checked, Jenkins will prevent the project from building when a child of this project is in the queue, or building. So this appears to behave as designed (or at least as documented). 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Daniel Beck commented on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation I'm not sure what documentation you're reading (appears to be perhaps the "?" pop-up) Yep, inline help. 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". Needs a balance between short enough to be suitable as label, and being long enough to properly explain what it does. You're right that it's probably too short in this case. 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? Checking the sources, it appears that it always should have behaved like this. Too many changes between the two releases to easily determine what was fixed and when, but it you could narrow it down I'll take another look. There's a chance it's related to a long standing queue concurrency bug that only recently was fixed. Third, perhaps there are useful scenarios to block if simply queued (but none come to mind for my immediate usage). Many features are best left to plugins to allow users to customize and configure Jenkins as much as they want while not overloading the default UI out of the box. Plugins could certainly achieve this with the existing extension points. 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? The jenkinsci-users mailing list can best provide answers to your Jenkins usage questions. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28136) Won't run either job when both queued in an upstream/downstream situation
Douglas Blondin commented on JENKINS-28136 Wont run either job when both queued in an upstream/downstream situation 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? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
