With respect to the current Win10 worker, the older system status looks
like my fault - it appears stuck waiting for a manual reboot for prior
updates (I guess at some point it stopped doing it automatically), so I'll
get that caught up.
Personally, I'd prefer not to encode additional release deta
On 29/03/2021 3:29 am, Jeremy Kloth 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 onc
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 ha
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 shoul
