| As an example of the problem: I have a number of generic build slaves. Platform Labeler gives them the automatic label "Fedora" (among others). I also have a special performance test slave, with the special label "performance". This slave is configured with the usage restriction "Only build jobs with label restrictions matching this node". But it too gets the automatic label "Fedora" (which is not visible when configuring the slave: out of sight, out of mind). Any jobs which are configured to run on a generic label like "Fedora" are currently free to select the performance slave, but by selecting "Only build jobs with label restrictions matching this node" I was hoping to avoid this. (I suppose I will have to specify "Fedora && !performance" on these jobs as a workaround.) Disabling the automatic labels for a particular slave (or "Only build jobs with label restrictions matching this node's explicit labels") would be a cleaner option for me, since only jobs with the explicitly listed label ("performance") would run on the node. This sounds like Kevin Cai's first option in the description. |
