[Buildbot-devel] Multiple change-sources, multiple projects, single buildbot machine?

[John Pye]

Hi all,

On the little buildbot that I set up last week, I've been thinking about 
hosting automated testing of a few different small projects that I'm 
involved with. These projects have different change-sources: a local 
CVS, a remote CVS (Sourceforge) and a remote SVN (for our ASCEND project)

What would be the suggested way for configuring buildbot in this case?

I thought about multiple buildmaster accounts, a single buildmaster 
account with multiple directories. I thought about a single buildmaster 
with multiple 'PB' ports for change notifications from each of those, 
with three local cron jobs to grab the changes.

What's going to be the best approach to ensure that the machine doesn't 
fall over when things get busy?

Cheers
JP

-- 
John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia
http://pye.dyndns.org/