[Buildbot-devel] Playing nice on loaded buildslaves - sharing buildmasters between projects?

[John Carr]

You can have separate waterfalls. It's not pretty.

I used to put each project it its own category. Then something like this:

https://gist.github.com/1345508

To add a waterfall url handler for each category.

You could refactor this to have a Waterfalls resource that would something like this:

https://gist.github.com/3917334

Then you don't have to change the code every time you add a new category.

(BOTH GISTS COMPLETELY UNTESTED)

John


On 19 Oct 2012, at 08:48, Dan Kegel <dank at kegel.com> wrote:

> Perhaps unwisely, I have a whole bunch of buildslaves
> running in lxc containers (very lightweight vm's) on one
> machine, all talking to different buildmasters.
> If I'm not careful, I can run out of memory because too
> many builds happen at once.
> 
> A few ideas for how to prevent this:
> 
> - don't run so many buildslaves on one physical machine
> - use a single buildmaster
> - vary the hour and minute parameters to timed.Nightly() in master.cfg.
> - make the build script use -j1 instead of -n$ncpus when load is high
> - make build script terminate on startup if the load is really high.
> - use distcc and let it handle load balancing
> 
> I'm not sure how I would go about using a single buildmaster
> for all projects, and still have separate waterfalls, one
> for each project.  Is that possible?
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel