On Mon, Mar 29, 2021 at 12:58 PM Jeremy Kloth
wrote:
> While I appreciate the information, I believe that the names being
> referred to here are the worker IDs. I'm wondering about the worker
> *display* names, those that are shown in the various status views. In
> the buildmaster config, this
> > On Sun, Mar 28, 2021 at 12:29 PM Jeremy Kloth
> > wrote:
> > > Mostly I'm looking to differentiate the would be two Win10 workers
> > From: "David Bolen"
> > Personally, I'd prefer not to encode additional release details in the
> > worker name itself, leaving that stable, but it is a detail
- Original Message -
> From: "David Bolen"
> To: "Jeremy Kloth"
> Cc: "python-buildbots"
> Sent: Monday, March 29, 2021 4:29:29 AM
> Subject: [Python-buildbots] Re: buildmaster worker naming
>
> With respect to the current Win10 wo
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
