-
Story
-
Resolution: Unresolved
-
Major
It has been pointed out multiple times that some of the terminologies in Jenkins have been confusing especially for new users. 2.0 is a great opportunity to take a fresh look on the terminology and try to sort them out.
This is a blanket ticket to track what we are taking on, what are rejected, and what are pushed out of scope.
See the linked tickets for individual proposed items.
This epic is likely the one that drives most bikeshedding. So inputs are welcome, but I suspect at some point we'd make a decision and stick with it.
- is related to
-
JENKINS-42816 Agent terminology cleanup
- Open
-
JENKINS-7628 Resolve naming inconsistencies in hudson interface - terminology
- Resolved
-
JENKINS-21706 Terminology of lastUnsuccessfulBuild is unclear
- Resolved
-
JENKINS-10763 Definition of the terms Stable/Unstable/Failed; Successful/Unsuccessful and so on
- Open
-
JENKINS-27268 "dumb" slave?
- Resolved
-
JENKINS-31160 Update Jenkins UI not to call everything a "Build"
- Open
-
JENKINS-33007 Rename "node" to "agent" throughout Jenkins
- Open
-
JENKINS-33008 Rename or alias `node` keyword to `agent`
- Resolved
-
JENKINS-29522 Rename master/slave to manager/worker
- Closed
-
JENKINS-35449 Review and document all remaining uses of the term "slave" in core
- Open
-
JENKINS-35448 File issues against plugins in jenkinsci github org that use the term "slave" for agents
- Open
-
JENKINS-35450 Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
- Open
-
JENKINS-35451 Change name of "slave.jar" to "agent.jar"
- Resolved
-
JENKINS-35452 Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp"
- Closed