Looks to be two separate issues here.

1. When a multi-configuration project is launched it is assigned to a slave node but not an executor. Even thought the project isn't using an executor is marks the node as not being idle.
2. The mapping of tasks from a multi-configuration project occurs in a batch. So the status and number of executors available to a node isn't updated as each task is mapped.

Will continue investigation.

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.
 
 

Reply via email to