[Buildbot-devel] Q: How do simultaneous change-set builds not collide?

[Axel Hecht]

My I dare to clarify what Dustin said. Ohoh ;-)

There is at most one Build for one Builder on each slave that is
connected and associated with the Builder. So, for the master, they
run in parallel, but on the slave, they're serialized.

Regarding parallism, it's usually OK to build with make -j (number of
cores + 1). At least if your build system can do that. I think the +1
here is for the master gnu make process which just sits there anyway.
So, if your build system does not support parallel builds, you could
likely run a few slaves in parallel on modern machines without slowing
down the individual builds too much.

And, of course, you can just throw hardware at the problem with
buildbot, i.e., buy a new machine and set it up to run extra slaves.

Axel

2008/5/16 Dustin J. Mitchell <dustin at zmanda.com>:
> On Thu, May 15, 2008 at 11:18 PM, Michael Kent <mrmakent at cox.net> wrote:
>> OK, so maybe my understanding of what buildbot will do is completely
>> off.  If for one builder, if it is currently running a build of a
>> change-set, and a second commit triggers another change-set build, are
>> they serialized (that is, the first build must finish before the second
>> starts)?
>
> Yes, that's correct.
>
> You could work around it by running multiple buildslaves on the same
> machine.  I'm dubious as to how practical it will be to run multiple
> builds simultaneously on the same machine, but I'm sure you have your
> reasons.
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>