|
||||||||
|
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 think the ideal way to solve this is to have a multi-project throttle category that you assign to all your jobs.
The multi-project throttle category should be able to have high limitations or no limitations at all.
If you then create:
jobA and jobB with the limitations 0/0 they should be able to run concurrently up to the multi-project throttle category limitations.
jobC with the limitations 1 per node, jobC should only run on a node if no other job with the throttle category runs on the node.
jobD with the limitations 1 in total, jobD should only run if no other jobs of this category is running.
The UI to support this is already there, I have tried to set this up since I thought that it should work before I saw this issue![]()