I think currently we use the term master for 2 different things.
First we have Jenkins orchestrating the builds, here the term controller
probably fits best but also server seems to fit for me
Second the server is also just plain agent (more or less). For this we
could use the term "main" as the default label.
On 15.06.2020 17:18, Matt Sicker wrote:
A master key is a particular type of universal key used for unlocking
multiple different locks. In this case, the master key in Jenkins is
used to unlock all the other encrypted data. It sort of makes sense.
On Mon, Jun 15, 2020 at 10:04 AM Angélique Jard <[email protected]> wrote:
My preference goes to "controller", "server" make me think somehow to the hardware
physical machine. "Coordinator" is fine also (in the link tools.ietf in previous post) but a bit
hard to pronounce.
As a non english native speaker (but french), I have some issue with "valet" and
"majordomo" which have fix gender in french and are all male. I know that it's not like
that in english but I think it's better to tell it now.
As a music player I also like "conductor" (as musical director) this is how I
see my Jenkins instance when I use it, that orchestrate agents, Jenkinsfile could be the
music sheet :) ....
On Monday, June 15, 2020 at 4:00:27 PM UTC+2 Antonio Muñiz wrote:
In spanish the term "Master" ("Maestro"), when used in isolation (no "slave" in
the context), has no negative connotations. Its main use is to describe someone very skilled in some matter
(often used for artisans).
I might be suffering of language bias, just wanted to give some "non english native
speaker" perspective to the conversation.
El lun., 15 jun. 2020 a las 7:56, Justin Harringa (<[email protected]>)
escribió:
Personally I thank the community for having already starting down this path.
I tend to like leader or controller from
https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1
but I could also see server working. The difficulty I would see with
primary/active is that folks who run Jenkins would have a bit of a conflict of
terminology there.
Take care all.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3411fed5-7e21-454a-b285-f719f07c1b3ao%40googlegroups.com.
--
* Antonio Manuel Muñiz
* amunizmartin.com
* [email protected]
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/56742697-234e-4d29-b613-fcc13d072ed7n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/40803353-626b-7cbe-f0e1-84f7727885cc%40gmx.de.
