The slave labels should accomplish this, no?
It's not waterproof, but as long as everyone cooperates, setting the
correct labels on the correct jobs and slaves should do the trick of
keeping the jobs off those slaves where they don't belong, no?
> But as far as I know, slave labels don't work for our purpose.
> We need to prevent jobs from being built on slaves not authorized for
If you don't trust users to create jobs properly, don't let them create jobs.
> For example, job authors may forget to set correct labels on their
> or even forget to enable 'restrict slaves' option by accident.
Set the 'leave this machine for tied jobs only' configuration option on all of
the slaves so you have to set a label or it won't build. Also, people learn
fairly quickly in an environment where there are a mix of OS versions in the