> On 14. Jun 2020, at 02:46, Mark Waite <[email protected]> wrote:
>
> Using the word 'valet' instead of 'master' to refer to the node that executes
> inside the original Jenkins Java process. Replace it with the term you prefer
> • Redirect requests from /computer/(master)/ to /computer/(valet)/
Good idea.
> • Assign the label 'valet' to the node that executes inside the
> original Jenkins process
> • Assign the NODE_NAME="valet" env var to that node instead of
> NODE_NAME="master"
> • Replace 'master' with 'valet' in help-label.html for AbstractProject
> • Change display name of root node from 'master' to 'valet'
> • Change the Jenkins#getSelfLabel() to return the label atom of "valet"
> instead of "master"
> • Convert tests that reference agent labeled 'master' to use label
> 'valet'
Right, I assumed the basic 'change X to Y' was given and only listed things
that needed doing on top of that. Good to have a complete list in advance
though.
> Things that would not change:
> • The jenkins.security.Roles (internal concept only, not shown to users)
Interesting. While we could change the string used, the field is what's
actually used, and then we're back to how much we want to break things. We may
be able to attempt this one, but since everyone is just using the objectionably
named *To*Callables anyway that we cannot really change.
> • Name of the key file in security/master.key (internal concept, not
> shown to users)
Is this the same kind of 'master' we're trying to get rid of? I haven't seen
'master key' having a historical association with slavery.
--
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/FDDEAEF6-517E-4914-952B-6EC39EDC27DE%40beckweb.net.
