On Fri, Oct 6, 2017 at 4:33 PM, Craig Rodrigues <rodr...@crodrigues.org> wrote:
> Based on my experiments, I think it is safe to perform the migration as > follows: > > 1. Update the buildbot master to buildbot 9 + Python 3. Leave the > buildbot workers/slaves alone. They should be > able to successfully connect to the new buildbot master and work. > > 2. For the buildbot worker/slave maintainers, give them the following > options: > > a. Upgrade the buildbot worker to buildbot 9 + Python 3 (MOST > PREFERRED) > b. Upgrade the buildbot worker to buildbot 9 + Python 2 (LESS > PREFERRED, BUT WILL WORK) > c. Leave the buildbot slave alone at buildbot 8 + Python 2 (LEAST > PREFERRED, BUT WILL WORK) Yes, my own preference would be to do workers last. It sounds to me like most of the benefits of this change accrue on the master side (eliminating our custom version) and at least for my part, I'd prefer not to be critical path to allowing that upgrade to proceed. Over a longer period, I'm curious about the preferences - are there concrete benefits in our environment of 0.9 over 0.8 on the worker side? E.g., what does upgrading bring on the worker side? In some cases an upgrade is trivial, but I've still got a few local tweaks on the Windows side that, while probably not too difficult to port, incur cost only worth doing if there is a concrete requirement or benefit. Oh, and I can offer any of my Windows workers for interoperability testing if you'd like me to temporarily configure them to an additional master. At least one of them (XP) is probably not worth the effort of getting to (a) vs. (b). -- David _______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
