Hi Jeremy, Renaming is fine, and we’ve done it previous for our FreeBSD workers. As far as I’m aware the only consequential consideration is that build URLs include(?d) worker names, which were no longer valid after the rename.
Newer buildbot may have changed this to use id’s instead, but I haven’t looked for that specifically. > On 29 Mar 2021, at 3:29 am, Jeremy Kloth <jeremy.kl...@gmail.com> wrote: > > I'm looking to add another Windows 10 worker to the "buildbot fleet". > Since Win10 updates semi-regularly, is it an issue if the worker name > (BuilderConfig.name) gets changed over the lifetime of the worker? > Currently it would be "Windows10 20H2", but once the next update is > released, the name should be updated to "Windows10 21H1". > > Mostly I'm looking to differentiate the would be two Win10 workers, > but there is a bit of practicality to this as well. Each update (or > version, as it were) does bring changes and features to the base OS, > which can be noticed by test_locale failing > (https://bugs.python.org/issue37945) on recent versions, but not on > the current Windows 10 worker (at version 1803). > > Related to that, if renaming a worker is OK over its lifetime, then > would it be permissible to suffix "1803" to the current Win10 worker > name? > > I'll submit the PR for the new worker once there is clarification. > > Thanks for your time. > > -- > Jeremy Kloth > _______________________________________________ > Python-Buildbots mailing list -- python-buildbots@python.org > To unsubscribe send an email to python-buildbots-le...@python.org > https://mail.python.org/mailman3/lists/python-buildbots.python.org/ > Member address: koobs.free...@gmail.com _______________________________________________ Python-Buildbots mailing list -- python-buildbots@python.org To unsubscribe send an email to python-buildbots-le...@python.org https://mail.python.org/mailman3/lists/python-buildbots.python.org/ Member address: arch...@mail-archive.com
