-
Improvement
-
Resolution: Unresolved
-
Minor
There is an inconsistent mixture of "slave" and "node" throughout the Jenkins core UI.
For example, viewing the details of a slave shows the title "Slave foo", the breadcrumb "Jenkins > Nodes > foo", and the URL /computer/foo.
As per JENKINS-27268, all instances of "slave" were renamed to "agent", and the changes were merged into the Jenkins 2.0 branch.
Ideally we should take this chance to stop using the word "node" — I think it has much less meaning for regular users, and in general, compared to "agent".
i.e. everywhere where "Node" is at the moment should become "Agent".
- is related to
-
JENKINS-31095 2.0: Jenkins terminology sweep
-
- Open
-
- links to
Tyler reminded me that the Jenkins master is available for build execution, which is perhaps why we have the mixture of references to nodes and slaves.
But it wouldn't be so bad to call everything "agent" anyway? Master already has an arguably confusing dual purpose: managing configuration and everything, and also being a build executor (in an out-of-the-box Jenkins install). So we could say that the master has an agent embedded within it.