|
||||||||
|
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.
One possible pattern I've just noticed is that it seems that the parent job only consumes a real executor if there already is a flyweight job running on the node. I have all of my matrix parents running on a single node to ensure that the initial checkouts are as quick as possible, and in the past, many flyweight jobs would run on this node happily. Since the upgrade, I've only ever observed one running, and additional jobs that should be flyweight jobs, consume the executor on this node.