[Buildbot-devel] User Question: 1 builder -> 2 buildslaves

sergio borghese sergio.borghese at gmail.com
Sat May 18 16:54:09 UTC 2013


Hi All,

just tried Ludovic & Mattias suggestion sucessfully, thanks to both of you
for the quick reply.
I was misunderstanding the 1-builder : N-slaves use case model
As Ludovic explaind, it is more for load balancing, rather than
distributing on different slaves.
My buildmaster cfg file is rather structured, so I found quite easy to add
an extra builder :)

Many Thanks
Sergio


On Sat, May 18, 2013 at 6:44 PM, Ludovic Chabant <ludovic at chabant.com>wrote:

>
> On Sat, May 18, 2013 at 8:24 AM, sergio borghese <
> sergio.borghese at gmail.com> wrote:
>
>> When the SVNPoller notice something has changed in the repo, I was
>> expecting the build process to start on both hosts, to test the build on
>> both O.S.
>> It seams the build process starts only on one of the slaves instead, and
>> the one that is started seem random (I did not see a pattern)
>>
>
> Yes, you just declare what builders *can* run on what buildslaves, so that
> buildbot can do a bit of logic for distributing builds across buildslaves
> when lots of events come in (load balancing, etc).
>
> If you have 2 builders that are not completely equivalent (they do the
> same thing but must run on different OSes), the easiest way to handle that
> would be to, in fact, create 2 builders. Because the master.cfg file is a
> regular Python file, you can have a bit of logic to generate the same
> builder instance or builder factory twice. Then you can link one builder to
> one slave, and the other to the other slave. Then you trigger both builders
> from your scheduler.
>
> --
>    l u d o .
>    . 8 0 17 80
>



-- 
preferisco ammazzare il tempo,
preferisco sparare cazzate,
preferisco fare esplodere una moda,
preferisco morire d'amore.
(Caparezza)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130518/cadbf544/attachment.html>


More information about the devel mailing list