[users at bb.net] Structure of buildbot installation for multiple projects

[Benoît Allard]

On Thu, 21 Jul 2016 08:34:19 +0200
Paulo Matos <pmatos at linki.tools> wrote:

> Hello,
> 
> I am setting up a new buildbot infrastructure for multiple projects.
> The issue here is that I haven't understood exactly what's the
> recommendation on how to do this. I have 3 projects, 4 computer for
> work. I intend to use 0.9rc.
> 
> * Do I need 1 master per project?
> * Do I need 1 worker per project, per computer?
> 
> I noticed that there multi project support in buildbot which in this
> case would mean I have 1 pc for the master and the remaining for
> workers. But then do I have 1 worker / cpu (totalling 3) or 1 worker /
> cpu / project (totalling 9) connecting to the same master?
> 
> It would be great if someone could clarify what's the best way going
> forward.

The point is, there is no general rule of what you should do. Buildbot
is meant as a framework, and as such is built to be flexible and adapt
to anyone's idea. It's very good at that by the way !

Usually, you want to have one master (= one web interface), to
orchestrate your different workers. You probably want to install one
worker per machine you have (+ maybe one on the master itself if it's
not very busy already)

One key concept you are not mentioning here are the 'builders'.
builders perform a predefined list of actions. You can have as many
builders as you want on a worker. See it this way, machines are usually
setup to be able to perform some specific tasks (some have tools to
build documentation, other have compiler installed, they can have
different OSes, ...), so each worker will have a purpose. Based on the
purpose of your builder, you will then be able to assign each builder
to a worker.

Does that helps you moving forward ?

Regards,
Ben.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.buildbot.net/pipermail/users/attachments/20160722/d13ef679/attachment.bin>