[Buildbot-devel] one slave... for multiple masters?

[john gale]

I've been thinking a lot about creating a pool of machines to use for  
many projects.  Similar to the over-used "cloud computing" concept,  
you would be able to create one master per overarching project, and  
then have a pool of build and test slaves that can be allocated based  
on who needs them.

There are ways to do this clumsily; say, set up multiple configuration  
files on each slave, pointing to each different master.

But is there a way to do this more gracefully?  Specifically, I don't  
want people stepping on each others' toes.  When one slave is being  
used for testing, it can't host any other projects' unit tests.  Very  
much like the SlaveLock feature...  except I'm hoping across multiple  
masters.

There might not be a way to do this currently, but does it look like  
it could be feasible?  I don't have time now, but soon may be able to  
devote some serious resources to this problem.

thanks,

	~ john

=================
support the arts!
www.smadness.com

updated October 12, 2005