|
||||||||
|
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.
I cannot think of a good solution to this issue. Moving between executors, or changing a job from "heavy-weight" to fly-weight isn't really possible AFAIK.
The best approach I can think of right now is to limit the number of matrix jobs allowed to run in parallel using something like Throttle Concurrent Builds, but that's of course a different limitation (you don't care about how many matrix parents are running after they've finished SCM operations).