Details
-
Type:
Epic
-
Status: In Progress (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Epic Name:Agent terminology cleanup
-
Similar Issues:
Description
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: https://github.com/search?q=org%3Ajenkinsci+slave&type=Code. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them.
Newcomer-friendly issues
There are many areas where anyone could help, deep Jenkins expertise is not required
- Cleanup plugin built-in documentation and documentation in Jenkins repositories
- GitHub Query: https://github.com/search?q=org%3Ajenkinsci+slave&type=Code
- If you work on these tasks, in the most of the cases you can just use GitHub web interface to edit files and submit pull requests.
- Newcomer-friendly tasks in this EPIC: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816
- Report issues. If you see something in the Jenkins UI or on our website, please do not hesitate to report it
- Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there
- jenkins.io website: https://github.com/jenkins-infra/jenkins.io/issues
Scope
Trivial changes:
- Jenkins Documentation (jenkins.io, plugin docs, etc.)
- Built-in plugin documentation and Web UI
- Localization files - "slave" equvalents in other languages
- 3rd-party blogposts
- Any code which is not a part of public AP or persistence modeI: private methods, local variables, comments, etc.
Non-trivial changes which may impact compatibility:
- Plugin Names
- REST API endpoints
- Symbols for JCasC/JobDSL/Pipeline
- Class Names and API where feasible (Retaining binary compatibility may require a massive effort)
- Library and module names
- Plugin labels and filters
- etc.
Attachments
Issue Links
- is related to
-
JENKINS-51320 Comb through text in base Jenkins and complete changes of "slave" to "agent"
-
- Resolved
-
-
JENKINS-31095 2.0: Jenkins terminology sweep
-
- Open
-
- relates to
-
JENKINS-65398
Terminology update for master, whitelist, blacklist
-
- Open
-
- links to
(2 links to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Nicolas De Loof [ ndeloof ] | Oleg Nenashev [ oleg_nenashev ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | JENKINS-42842 [ 179844 ] |
| Epic Child | JENKINS-42843 [ 179845 ] |
| Epic Child | JENKINS-42844 [ 179846 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child | JENKINS-42848 [ 179851 ] |
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child |
|
| Epic Child | JENKINS-35450 [ 171247 ] |
| Epic Child | JENKINS-35449 [ 171246 ] |
| Epic Child | JENKINS-43144 [ 180260 ] |
| Assignee | Oleg Nenashev [ oleg_nenashev ] |
| Labels | jenkins2.0 |
| Epic Child |
|
| Epic Child |
|
| Link |
This issue is related to |
Jenn Briden
made changes -
| Epic Child |
|
| Epic Child |
|
| Labels | jenkins2.0 | fosdem2019 jenkins2.0 |
Josh Soref
made changes -
| Remote Link | This issue links to "windows-slaves-plugin#17 (Web Link)" [ 22760 ] |
| Epic Child |
|
| Labels | fosdem2019 jenkins2.0 | fosdem2019 hacktoberfest jenkins2.0 |
| Epic Child | JENKINS-35448 [ 171245 ] |
| Assignee | Oleg Nenashev [ oleg_nenashev ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Epic Child | JENKINS-60587 [ 203714 ] |
| Epic Child |
|
| Remote Link | This issue links to "windows-slaves-plugin#17 (Web Link)" [ 22760 ] |
| Epic Child | JENKINS-60827 [ 204177 ] |
| Epic Child | JENKINS-61302 [ 204882 ] |
| Epic Child | INFRA-2513 [ 205067 ] |
| Description | Just to keep a track of missing renamings when I occasionally notice them |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
| Labels | fosdem2019 hacktoberfest jenkins2.0 | fosdem2019 hacktoberfest jenkins2.0 newbie-friendly |
| Labels | fosdem2019 hacktoberfest jenkins2.0 newbie-friendly | fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly |
| Epic Child | JENKINS-61903 [ 205775 ] |
| Epic Child | JENKINS-61904 [ 205776 ] |
| Summary | Slave to Agent renaming leftovers | Agent terminology cleanup |
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
| Labels | fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly | fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap |
| Labels | fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap | hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap |
| Remote Link | This issue links to "GitHub Query (Web Link)" [ 24928 ] |
| Epic Child |
|
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] * Report issues. If you see something in the plugin or on our website, please do not hesitate to report it ** Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there ** jenkins.io website: [https://github.com/jenkins-infra/jenkins.io/issues] h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
| Labels | hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap | agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap |
| Labels | agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap | agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap ux |
| Remote Link | This issue links to "GitHub Query (Web Link)" [ 24928 ] |
| Remote Link | This issue links to "Leftovers: GitHub Query for the jenkinsci GitHub organization (Web Link)" [ 25006 ] |
| Remote Link | This issue links to "Leftovers: jenkins.io contents (Web Link)" [ 25007 ] |
| Remote Link | This issue links to "HOWTO: Migrating old documentation to jenkins.io (Web Link)" [ 25008 ] |
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in repositories. GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] * Report issues. If you see something in the plugin or on our website, please do not hesitate to report it ** Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there ** jenkins.io website: [https://github.com/jenkins-infra/jenkins.io/issues] h3. Scope Renaming scope includes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * 3rd-party blogposts * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Any other code: local variables, class fields, etc. * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in Jenkins repositories ** GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] ** If you work on these tasks, in the most of the cases you can just use GitHub web interface to edit files and submit pull requests. * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] * Report issues. If you see something in the Jenkins UI or on our website, please do not hesitate to report it ** Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there ** jenkins.io website: [https://github.com/jenkins-infra/jenkins.io/issues] h3. Scope Trivial changes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Localization files - "slave" equvalents in other languages * 3rd-party blogposts * Any code which is not a part of public AP or persistence modeI: private methods, local variables, comments, etc. Non-trivial changes which may impact compatibility: * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Library and module names * etc. |
| Labels | agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap ux | agents documentation hacktoberfest help-wanted jenkins2.0 localization newbie-friendly roadmap ux |
| Description |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in Jenkins repositories ** GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] ** If you work on these tasks, in the most of the cases you can just use GitHub web interface to edit files and submit pull requests. * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] * Report issues. If you see something in the Jenkins UI or on our website, please do not hesitate to report it ** Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there ** jenkins.io website: [https://github.com/jenkins-infra/jenkins.io/issues] h3. Scope Trivial changes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Localization files - "slave" equvalents in other languages * 3rd-party blogposts * Any code which is not a part of public AP or persistence modeI: private methods, local variables, comments, etc. Non-trivial changes which may impact compatibility: * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Library and module names * etc. |
"slave" terminology was deprecated in Jenkins 2.0, but there are still occurrences in Jenkins Plugins and documentation: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code]. We need to clean it up. This EPIC keeps a track of missing renaming when we occasionally notice them. h3. Newcomer-friendly issues There are many areas where anyone could help, deep Jenkins expertise is not required * Cleanup plugin built-in documentation and documentation in Jenkins repositories ** GitHub Query: [https://github.com/search?q=org%3Ajenkinsci+slave&type=Code] ** If you work on these tasks, in the most of the cases you can just use GitHub web interface to edit files and submit pull requests. * Newcomer-friendly tasks in this EPIC: [https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%20newbie-friendly%20and%20%22Epic%20Link%22%20%3D%20JENKINS-42816] * Report issues. If you see something in the Jenkins UI or on our website, please do not hesitate to report it ** Jenkins core and components: Jenkins Jira or GitHub Issues, depending on a component. If you report issues in Jira, please reference the JENKINS-42816 EPIC there ** jenkins.io website: [https://github.com/jenkins-infra/jenkins.io/issues] h3. Scope Trivial changes: * Jenkins Documentation (jenkins.io, plugin docs, etc.) * Built-in plugin documentation and Web UI * Localization files - "slave" equvalents in other languages * 3rd-party blogposts * Any code which is not a part of public AP or persistence modeI: private methods, local variables, comments, etc. Non-trivial changes which may impact compatibility: * Plugin Names * REST API endpoints * Symbols for JCasC/JobDSL/Pipeline * Class Names and API where feasible (Retaining binary compatibility may require a massive effort) * Library and module names * Plugin labels and filters * etc. |
| Assignee | Oleg Nenashev [ oleg_nenashev ] | Carlos Sanchez [ csanchez ] |
| Assignee | Carlos Sanchez [ csanchez ] |
| Component/s | other [ 15490 ] |
| Remote Link | This issue links to "Leftovers: "esclave" in french localization (Web Link)" [ 25217 ] |
| Epic Child |
|
| Epic Child | JENKINS-62791 [ 207006 ] |
| Epic Child | JENKINS-62833 [ 207057 ] |
| Epic Child | JENKINS-62925 [ 207252 ] |
| Epic Name | Slave to Agent renaming leftovers | Agent terminology cleanup |
| Epic Child |
|
Jacob Walls
made changes -
| Epic Child | JENKINS-63301 [ 207672 ] |
| Link | This issue is related to JENKINS-31095 [ JENKINS-31095 ] |
| Epic Child | JENKINS-63660 [ 208316 ] |
| Epic Child | JENKINS-64375 [ 209468 ] |
| Link | This issue relates to JENKINS-65398 [ JENKINS-65398 ] |
| Epic Child | JENKINS-65437 [ 211110 ] |