|
||||||||
|
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.
Thanks for the feedback Christian!
I don't know if using the threshold inputs on the Job configuration page is the right place to do this.
But I think we could implement this same support by moving the "blocking" part from the Job configuration into the Global configuration where we define the Categories. If we allowed category B to be blocked by category A.
This way we could allow category A to completely block all jobs in category B from executing until all queued jobs from category A have completed.
This would allow both categories to have their own separate throttle limits which would not interfere with each other.