[Python-buildbots] Re: buildmaster worker naming
- 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 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 details in the > worker name itself, leaving that stable, but it is a detail that could be > included in the worker info field, so I'll get that adjusted too. > > -- David > > > On Sun, Mar 28, 2021 at 12:29 PM 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 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: db3l@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: cstra...@redhat.com > > I'm doing the same thing. For example I have a cstratak-RHEL7-ppc64le named worker which indicated the architecture and the OS major version, however the minor version (7.9) is noted at the host's description. Whenever I'd update (e.g. from 7.8 to 7.9) I'd just change the description. -- Regards, Charalampos Stratakis Software Engineer Python Maintenance Team, Red Hat ___ 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
[Python-buildbots] Re: buildmaster worker naming
> > 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 that could be
> > included in the worker info field, so I'll get that adjusted too.
On Mon, Mar 29, 2021 at 7:41 AM Charalampos Stratakis
wrote:
> I'm doing the same thing. For example I have a cstratak-RHEL7-ppc64le named
> worker which indicated the architecture and the OS major version, however the
> minor version (7.9) is noted at the host's description. Whenever I'd update
> (e.g. from 7.8 to 7.9) I'd just change the description.
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 name forms the base of the builder names.
For example,
# (name, worker, buildfactory, stability)
("AMD64 Windows7 SP1", "kloth-win64", Windows64Build, STABLE),
("AMD64 Windows10", "bolen-windows10", Windows64Build, STABLE),
("AMD64 Fedora Rawhide", "cstratak-fedora-rawhide-x86_64",
UnixBuild, UNSTABLE),
("AMD64 FreeBSD Shared", "koobs-freebsd-564d", SlowSharedUnixBuild, STABLE),
where I want to change my worker to:
# update the `name` to reflect upgrades
("AMD64 Windows10", "kloth-win64", Windows64Build, STABLE),
# keep worker going until 3.8 EOL
("AMD64 Windows7 SP1", "kloth-windows7", Windows64Build, STABLE),
Worker IDs are already unique, I was hoping for guidance on the would
be duplicate display name (as shown on the status views aka
Waterfall). There currently isn't any other combination of (OS, arch,
build-conf) that do not result in a unique display name. Officially,
the installed OS is "Windows 10 Pro", I suppose I could go with that
or I'm making too much of the potential confusion on the status views.
Personally, I just have a page loaded for my worker that I check
periodically so *I* don't mind the duplication.
Thanks again.
--
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: arch...@mail-archive.com
[Python-buildbots] Re: buildmaster worker naming
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 name forms the base of the builder names. > Ah, yes, for my part you're correct we were referring to different things, probably due to the original use of worker, rather than builder (though the suggested text ought to have suggested builder to me). For myself I rarely consider builder names. My most common landing page is the workers summary page, then passing through the all builds summary for a worker or an individual builder summary page on the way to a specific build. In those cases the builder name is mostly noise to skip past when looking for the branch. I no longer have multiple builders on any worker, but when I did I only needed uniqueness within the worker. Of course, users of other status pages (I can't recall when I last used the waterfall) may have different needs, though they can always drill through to the worker for worker-level details. While I suppose the above argues for me not to care much about builder names or updates, it's then a more pragmatic issue of ease of my updating details in sync with the worker, for which the info file is simpler. It also feels more appropriate as a worker level detail rather than builder, though I'd agree Windows 10 and its feature upgrades complicates this point. -- David ___ 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
