|
Labels are used to restrict jobs to slaves, but also to assign tool installations to slaves.
Unfortunatly sometimes these labels are orthoganal.
For instance - our Linux JDK bundle would be used by all slaves that have the label "RH".
Jobs that need a linux machine would be tied to the label "RH".
All is well, but then we have a RH machine (call it machine X) that isn't the same rubber stamp template as the other redHat machines - and we don't want jobs tied to "RH" to be able to use that slave.
Unfortunatly as I found out the slave option "Leave this machine for tied jobs only" treats any label as equal so the jobs that run on it are the ones that have the explicit slaveName labelAtom set as well as the ones that that the generic label set.
The two possible workarounds are not nice.
1) update all jobs so that there requirements are (RH && ! slavename)
2) update all tool installations to add extra slave label and remove labels from slave.
It would be better for a new "Usage" model to be defined alongside
Node.mode.EXCLUSIVE and Node.mode.NORMAL to provide this requirement (say Node.mode.EXPLICIT)
|
