|
||||||||
|
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/groups/opt_out.
I've added an alternative computer.isIdle() check to check the actual executors to avoid having a node as not being idle when if it running the control multi-configuration project.
I added some randomness when retrieving the list of applicable executors in an attempt to better balance the projects launched by the multi-configuration project.
It is not possible to guarantee that in the case of multi-configuration projects that the least loaded node will be selected as the mapping is batched and the state of the nodes isn't updated during the batching.