-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.536 on RHEL5 x86_64
After installing Least Load plugin I now get parent matrix jobs scheduled on master. The thing is that I have set up number of executors on master to 0 as I don't want to have any jobs scheduled on master; master should only work as a dispatcher.
Although parent jobs actually do not perform builds, yet they still perform interaction with SCM which may not be available on master. I believe the plugin should not consider master node if it's been explicitly disabled.
[JENKINS-20216] Jobs are scheduled on master which has 0 executors
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?
Alexander Boyd
added a comment - It can be used to configure the master node; it was, in fact, first brought to my attention by someone on the mailing list with a similar problem to yours (but I've since lost the post).
Alexander Boyd
added a comment - It can be used to configure the master node; it was, in fact, first brought to my attention by someone on the mailing list with a similar problem to yours (but I've since lost the post).
Matrix parent jobs are scheduled as flyweight tasks, so they operate independently of how many executors are available on a given node. You could use something like https://wiki.jenkins-ci.org/display/JENKINS/Exclude+flyweight+tasks to force them to be run elsewhere.