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

Recommended plugins for 2.0 should refer to "agents" rather than "slaves"

      Some plugins on the recommended plugin list still refer to "slaves" rather than "agents" — prominently, this includes the "New item" text of the Pipeline plugin.

      This should ideally be fixed for all recommended plugins before the Jenkins 2.0 release.

      I will try to concentrate on the most popular plugins, as listed by Daniel's spreadsheet, and keep track of PRs from this ticket.

      Though of course anyone who wants to help is welcome

          [JENKINS-33369] Recommended plugins for 2.0 should refer to "agents" rather than "slaves"

          Christopher Orr created issue -
          Christopher Orr made changes -
          Environment Original: Jenkins 2.0-alpha-2
          Christopher Orr made changes -
          Description Original: I installed Jenkins 2.0 alpha-2, and installed the recommended plugins, and noticed that there are a lot of UI fields that have no inline help.

          Similarly, some plugins still refer to "slaves" rather than "agents" — prominently, this includes the "New item" text of the Pipeline plugin.

          Ideally, every single config field should inline help in English (as a start), and the help text should be unambiguous, and gramatically correct.

          I will try to concentrate on the most popular plugins, as listed by [Daniel's spreadsheet|https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit], and keep track of PRs from this ticket.
          Though of course anyone who wants to help is welcome :)
          New: Some plugins on the recommended plugin list still refer to "slaves" rather than "agents" — prominently, this includes the "New item" text of the Pipeline plugin.

          This should ideally be fixed for all recommended plugins before the Jenkins 2.0 release.

          I will try to concentrate on the most popular plugins, as listed by [Daniel's spreadsheet|https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit], and keep track of PRs from this ticket.

          Though of course anyone who wants to help is welcome :)
          Christopher Orr made changes -
          Link New: This issue is related to JENKINS-33366 [ JENKINS-33366 ]
          Kohsuke Kawaguchi made changes -
          Labels Original: 2.0 user-experience New: 2.0 2.0-planned user-experience

          Daniel Beck added a comment -

          I'd love to see how you're going to fix the SSH Slaves Plugin.

          Daniel Beck added a comment - I'd love to see how you're going to fix the SSH Slaves Plugin.

          Renaming from "SSH Slaves Plugin" to "SSH Agents Plugin" seems like a reasonable solution.

          Christopher Orr added a comment - Renaming from "SSH Slaves Plugin" to "SSH Agents Plugin" seems like a reasonable solution.

          Daniel Beck added a comment -

          Except it's really ambiguous: https://en.wikipedia.org/wiki/Ssh-agent

          Daniel Beck added a comment - Except it's really ambiguous: https://en.wikipedia.org/wiki/Ssh-agent

          Yeah, I forgot about SSH agents. Couldn't you have just said that in the first place?

          Indeed, there is already a Jenkins plugin with virtually the same name https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin

          Christopher Orr added a comment - Yeah, I forgot about SSH agents. Couldn't you have just said that in the first place? Indeed, there is already a Jenkins plugin with virtually the same name https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin

          Since the SSH connection is done to a node rather than an agent, maybe "SSH Nodes Plugin" would make sense.

          Antonio Muñiz added a comment - Since the SSH connection is done to a node rather than an agent, maybe "SSH Nodes Plugin" would make sense.

            Unassigned Unassigned
            orrc Christopher Orr
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: