-
Bug
-
Resolution: Unresolved
-
Major
-
support-core:2.69
The support core plugin is still using the terminology slave for the files / directory / error message it produces. For example the agent's directory are collected under nodes/slave/, agent's remoting version is shown as "Slave Version", ...
Those should be replaced accordingly with the term agent
Addiitonally 'master' must be renamed to 'controller' as per https://issues.jenkins.io/browse/JENKINS-65398
- blocks
-
JENKINS-65437 terminology update: remove the usage of the slave term
-
- Closed
-
[JENKINS-62925] terminology update: remove the usage of the master and slave terms
Epic Link | New: JENKINS-42816 [ 179816 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Link |
New:
This issue blocks |
Description |
Original:
The support core plugin is still using the terminology {{slave}} for the files / directory / error message it produces. For example the agent's directory are collected under {{nodes/slave/}}, agent's remoting version is shown as "Slave Version", ... Those should be replaced accordingly with the term {{agent}} |
New:
The support core plugin is still using the terminology {{slave}} for the files / directory / error message it produces. For example the agent's directory are collected under {{nodes/slave/}}, agent's remoting version is shown as "Slave Version", ...
Those should be replaced accordingly with the term {{agent}} Addiitonally 'master' must be renamed to 'controller' as per https://issues.jenkins.io/browse/JENKINS-65398 |
Summary | Original: Replace occurrences of 'slave' to 'agent' | New: terminology update: remove the usage of the master and slave terms |
Labels | New: terminology |
While I agree that UI terms should be replaced, we have to take care of changes in the bundle structure (we use a lot of slave and master folders) which will break our parsers