We have some hosts which we don't want included in the pool of available build hosts for jobs. We configure jobs to run against labels, this is now an issue with ubuntu-9.10-amd64, as not only do our build slaves run that, but also two machines on which build jobs should not run.

There are two separate reasons:
1) The machine is too small. For instance - the hudson master runs husdon, so it needs to only run Hudson, otherwise the website becomes unresponsive
2) The machine is special purpose. Our benchmarking machine(s) want to only be tied to the benchmarking jobs and not also run build jobs.

<mtaylor> lifeless: feature request: excluding hosts from auto labels...
<lifeless> mtaylor: file it in the tracker.
<lifeless> mtaylor: I don't know how to get at config stuff yet; but when I get some time I can ask. I don't have time ATM
<mtaylor> lifeless: no problem
<mtaylor> lifeless: for now I'm just manually adding a similar label and then using that in jobs
<lifeless> mtaylor: please do file it though!
<mtaylor> lifeless: (problem is, I have a host which is quite small which sure does run ubuntu-9.10 ... but I do not want it building/testing drizzle)
<mtaylor> lifeless: I will!
<lifeless> mtaylor: could the plugin determine 'size' for you?
<lifeless> e.g. cpus, memory, disk?
<lifeless> I'm thinking EC2 style 'small' 'medium' 'medium high memory' etc
<mtaylor> lifeless: perhaps... but also we have a machine which runs benchmarks and wants to only run benchmarks
<mtaylor> lifeless: so I want to tie it to a job and have no other jobs use it
<lifeless> sure
<mtaylor> lifeless: although the small/medium would certainly solve the first example