|
||||||||
|
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/groups/opt_out.
Hm... I am not really convinced by this explanation. I have master node configured with 0 executors, meaning that this node is not even listed on the node list and no jobs should be run there. It also did not happen until leastload plugin was installed. Now it happens that such flyweight task is scheduled on master, and master node then shows up in the node list running the task. Can the plugin you mentioned be used to configure master node? Or can it only be used for slaves?