On 19/10/2017 12:56 PM, Jim Rowan wrote:
If for some reason having the two parallel installations isn’t in your future,
I want to clarify one thing on your original proposal — you’d need to add a new
builder and a new scheduler, but you can reuse the same slave if you want the
same OS for the build context. Any number of builders can use a particular
slave (worker in the 0.9 terminology). Buildbot can queue up the builds for
your two projects if they happen to both want to fire at the same time and you
don’t want them to run simultaneously. In fact, if you have one machine
total, you may want to stick with only one installation and one defined slave
in order to orchestrate the load on that machine.
Thank you Jim. That makes sense. Both staging servers are on the same
physical hardware as the repos, trac and builbot. I'm not even using VMs.
It is an old Ubuntu server which has been upgraded at least twice to
16.04. For some reason each time it didn't upgrade buildbot. I suppose
that was deliberate.
Should I use apt to remove buildbot and pip to install a more modern
version?
0.8.1 is working fine and what persuaded me to adopt Pierre's suggestion
is that it would be nice to postpone avoidable disruption to what is
critical development infrastructure at the moment for the older project
but for both soon enough. I'm planning on migrating everything to a
newer system as soon as Trac is released with Py3. So there is
unavoidable disruption in my future.
Thanks
Mike
On Oct 18, 2017, at 6:04 PM, Mike Dewhirst <[email protected]> wrote:
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 <[email protected]
<mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________
users mailing list
[email protected]
https://lists.buildbot.net/mailman/listinfo/users
