On Mon, Mar 29, 2021 at 12:58 PM Jeremy Kloth <jeremy.kl...@gmail.com> 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
