[users at bb.net] additional project advice please

[Mike Dewhirst]

On 18/10/2017 7:23 PM, Pierre Tardy wrote:
> Hi Mike,
> Both options are reasonable.
> You can start over a new master.cfg, with new ports, and have a 
> separate master for your second project or you can reuse your first 
> master and improve the master.cfg to add your second project.
>
> I think it might just be easier to start with a new master. It will 
> allow you to start with a newer version of buildbot, which has had a 
> lot of improvement since 0.8.1
>
> Then you can think of merging the two master.cfg and reproduce your 
> old setup on your new master.
> With this method, you can keep your old master alone, and not disturb 
> the service for the legacy project.

I believe you have persuaded me.

Thanks Pierre

M


>
> Regards
> Pierre
>
> On Wed, Oct 18, 2017 at 5:51 AM Mike Dewhirst <miked at dewhirst.com.au 
> <mailto:miked at dewhirst.com.au>> wrote:
>
>     I have been running 0.8.1.2 for a long time with a single slave. It
>     watches the necessary repo and when it detects a commit it blows away
>     the staging server (on the same machine) and reassembles it from trunk
>     and runs the unit tests. I could not be happier.
>
>     Now I want to commence a second completely separate project.
>
>      From my reading of the excellent tutorial and 0.8.1.2 docs it seems I
>     just need to edit master.cfg to make a second builder  and a second
>     scheduler which nominates a second slave. It needs to execute more or
>     less the same set of build steps as the first one.
>
>     Is this a reasonable strategy?
>
>     Do I need to allocate a second set of ports?
>
>     Should I find a way to upgrade Buildbot to the current revision
>     beforehand?
>
>     Thanks for any pointers
>
>     Cheers
>
>     Mike
>
>     _______________________________________________
>     users mailing list
>     users at buildbot.net <mailto:users at buildbot.net>
>     https://lists.buildbot.net/mailman/listinfo/users
>