[Buildbot-devel] Managing many buildbots

Alexander Lorenz lorenz at testingtech.de
Tue Aug 29 08:20:49 UTC 2006

that depends:

the number of slaves is irrelevant for the waterfall display, it 
represents the number of _build(er)s_ .

so if you have one build that you just want to be able to run on five 
different machines (with the same os) for a faster build process, just 
assign all five slaves to one builder with your project factory, and 
you'll 'only' have 20 columns.

but if you want to build/test on five different environments, there is 
no clean way at the moment. :s

this is because buildbot was originally designed assuming a "one master 
per project" strategy.

i can understand you well, because i am in a similar situation and there 
are also others here who have proposed ideas.
up to now you can only avoid a 100 column waterfall by using some "dirty 
tricks" .

see the "aggregate waterfall view?" thread in this mailing group 
concerning both issues.



Einar Karttunen wrote:
> Hello
> I have a situation where I have about 5 machines
> that I want to use as buildbot-slaves and 20 projects.
> I would like to avoid having 5*20 = 100 configurations
> in total - is there a good way to avoid this?
> - Einar Karttunen
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list