Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42816

Agent terminology cleanup

    XMLWordPrintable

    Details

    • 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

      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

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Assignee Nicolas De Loof [ ndeloof ] Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1105 [ 179840 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42839 [ 179841 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42840 [ 179842 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42841 [ 179843 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42842 [ 179844 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42843 [ 179845 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42844 [ 179846 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42845 [ 179847 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42846 [ 179848 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-42848 [ 179851 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-43058 [ 180165 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-35451 [ 171248 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-35452 [ 171249 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-42512 [ 179439 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-35450 [ 171247 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-35449 [ 171246 ]
            bitwiseman Liam Newman made changes -
            Epic Child JENKINS-43144 [ 180260 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels jenkins2.0
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-48686 [ 187369 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-49661 [ 188590 ]
            danielbeck Daniel Beck made changes -
            Link This issue is related to JENKINS-51320 [ JENKINS-51320 ]
            jbriden Jenn Briden made changes -
            Epic Child JENKINS-51320 [ 190657 ]
            batmat Baptiste Mathus made changes -
            Epic Child JENKINS-52032 [ 191626 ]
            batmat Baptiste Mathus made changes -
            Labels jenkins2.0 fosdem2019 jenkins2.0
            jsoref Josh Soref made changes -
            Remote Link This issue links to "windows-slaves-plugin#17 (Web Link)" [ 22760 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-59427 [ 202010 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels fosdem2019 jenkins2.0 fosdem2019 hacktoberfest jenkins2.0
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-35448 [ 171245 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60587 [ 203714 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60608 [ 203837 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "windows-slaves-plugin#17 (Web Link)" [ 22760 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-60827 [ 204177 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-61302 [ 204882 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-2513 [ 205067 ]
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Labels fosdem2019 hacktoberfest jenkins2.0 fosdem2019 hacktoberfest jenkins2.0 newbie-friendly
            oleg_nenashev Oleg Nenashev made changes -
            Labels fosdem2019 hacktoberfest jenkins2.0 newbie-friendly fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly
            slide_o_mix Alex Earl made changes -
            Epic Child JENKINS-61903 [ 205775 ]
            slide_o_mix Alex Earl made changes -
            Epic Child JENKINS-61904 [ 205776 ]
            oleg_nenashev Oleg Nenashev made changes -
            Summary Slave to Agent renaming leftovers Agent terminology cleanup
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Labels fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap
            oleg_nenashev Oleg Nenashev made changes -
            Labels fosdem2019 hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "GitHub Query (Web Link)" [ 24928 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-62347 [ 206314 ]
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Labels hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap
            oleg_nenashev Oleg Nenashev made changes -
            Labels agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap ux
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "GitHub Query (Web Link)" [ 24928 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Leftovers: GitHub Query for the jenkinsci GitHub organization (Web Link)" [ 25006 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Leftovers: jenkins.io contents (Web Link)" [ 25007 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "HOWTO: Migrating old documentation to jenkins.io (Web Link)" [ 25008 ]
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Labels agents documentation hacktoberfest help-wanted jenkins2.0 newbie-friendly roadmap ux agents documentation hacktoberfest help-wanted jenkins2.0 localization newbie-friendly roadmap ux
            oleg_nenashev Oleg Nenashev made changes -
            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.
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ] Carlos Sanchez [ csanchez ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Carlos Sanchez [ csanchez ]
            oleg_nenashev Oleg Nenashev made changes -
            Component/s other [ 15490 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Leftovers: "esclave" in french localization (Web Link)" [ 25217 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-62714 [ 206904 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-62791 [ 207006 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-62833 [ 207057 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-62925 [ 207252 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Name Slave to Agent renaming leftovers Agent terminology cleanup
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-63166 [ 207503 ]
            jacobtylerwalls Jacob Walls made changes -
            Epic Child JENKINS-63301 [ 207672 ]
            froblesmartin Francisco Robles Martin made changes -
            Link This issue is related to JENKINS-31095 [ JENKINS-31095 ]
            froblesmartin Francisco Robles Martin made changes -
            Epic Child JENKINS-63660 [ 208316 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child JENKINS-64375 [ 209468 ]
            ajard A. Jard made changes -
            Link This issue relates to JENKINS-65398 [ JENKINS-65398 ]
            pierrebtz Pierre Beitz made changes -
            Epic Child JENKINS-65437 [ 211110 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
              Votes:
              6 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated: