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

Terminology update for master, whitelist, blacklist

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None
    • Terminology update for master, slave, whitelist, blacklist

      In July 2020 we  adopted the "controller" term instead of "master", and deprecated the "whitelist/blacklist" terms. There are many places where the old terminology still needs to be replaced.

      For example, deprecated term can be:

      • in UI files, like *.jelly, *.groovy, *.html
      • in logs that ends up in job console, or Jenkins console
      • in cli output
      • HTTP API
      • Documentation, README, code comments

      Changing master in other context (like git or any scm master branch) is out of scope of this Epic.
      We invite contributors to join us and participate in cleaning up Jenkins documentation, Web and CLI interfaces, and the codebase.

      Deprecated term To be replaced by
      master built-in when used for node/label
      controller (for everything else)
      slave agent (please use https://issues.jenkins.io/browse/JENKINS-42816 )
      whitelist allowlist (default but can be adapted to context)
      blacklist denylist or blocklist (default but can be adapted to context)

      If you are working on slave/agent replacement please use https://issues.jenkins.io/browse/JENKINS-42816

          [JENKINS-65398] Terminology update for master, whitelist, blacklist

          A. Jard created issue -
          A. Jard made changes -
          Epic Child New: JENKINS-58979 [ 201328 ]
          A. Jard made changes -
          Link New: This issue relates to JENKINS-42816 [ JENKINS-42816 ]

          A. Jard added a comment - - edited Some PR linked to this Epic https://github.com/jenkinsci/credentials-plugin/pull/197 – merged https://github.com/jenkinsci/gradle-plugin/pull/115 – merged https://github.com/jenkinsci/junit-plugin/pull/268 – merged https://github.com/jenkinsci/kubernetes-plugin/pull/981 – merged https://github.com/jenkinsci/git-plugin/pull/1077 – merged https://github.com/jenkinsci/config-file-provider-plugin/pull/117 – merged https://github.com/jenkinsci/ldap-plugin/pull/89 – merged https://github.com/jenkinsci/metrics-plugin/pull/98 – merged https://github.com/jenkinsci/credentials-binding-plugin/pull/128 – merged https://github.com/jenkinsci/ssh-slaves-plugin/pull/226 – merged https://github.com/jenkinsci/support-core-plugin/pull/227 – merged https://github.com/jenkinsci/windows-slaves-plugin/pull/32 – merged https://github.com/jenkinsci/docker-build-publish-plugin/pull/60 https://github.com/jenkinsci/promoted-builds-plugin/pull/152

          Oleg Nenashev added a comment -

          Should we keep agent cleanup in JENKINS-42816  ?

           

          Oleg Nenashev added a comment - Should we keep agent cleanup in  JENKINS-42816   ?  

          A. Jard added a comment -

          oleg_nenashev I have no strong opinion, I don't think that there are PRs with agent renaming only (it's often mainly controller and some agent in the way), but we can link both Epic maybe. But I can update the description to redirect to the other Epic for agent (I like to see the mapping all old word -> new word in one place).

          A. Jard added a comment - oleg_nenashev I have no strong opinion, I don't think that there are PRs with agent renaming only (it's often mainly controller and some agent in the way), but we can link both Epic maybe. But I can update the description to redirect to the other Epic for agent (I like to see the mapping all old word -> new word in one place).
          A. Jard made changes -
          Description Original: In 2016, the Jenkins community started changing the potentially offensive terminology within the project. The "slave" term was deprecated and replaced by "agent".

          In July 2020 we also [adopted|https://cd.foundation/blog/2020/08/25/jenkins-terminology-changes/] the "controller" term instead of "master", and deprecated the "whitelist/blacklist" terms. There are many places where the old terminology still needs to be replaced.

          For example, deprecated term can be:
           * in UI files, like *.jelly, *.groovy, *.html
           * in logs that ends up in job console, or Jenkins console
           * in cli output
           * HTTP API
           * Documentation, README, code comments

          Changing master in other context (like git or any scm master branch) is out of scope of this Epic.
          We invite contributors to join us and participate in cleaning up Jenkins documentation, Web and CLI interfaces, and the codebase.


          ||Deprecated term||To be replaced by||
          |master|controller|
          |slave|agent|
          |whitelist|allowlist|
          |blacklist|denylist|
          New: In July 2020 we  [adopted|https://cd.foundation/blog/2020/08/25/jenkins-terminology-changes/] the "controller" term instead of "master", and deprecated the "whitelist/blacklist" terms. There are many places where the old terminology still needs to be replaced.

          For example, deprecated term can be:
           * in UI files, like *.jelly, *.groovy, *.html
           * in logs that ends up in job console, or Jenkins console
           * in cli output
           * HTTP API
           * Documentation, README, code comments

          Changing master in other context (like git or any scm master branch) is out of scope of this Epic.
           We invite contributors to join us and participate in cleaning up Jenkins documentation, Web and CLI interfaces, and the codebase.

          ||Deprecated term||To be replaced by||
          |master|controller|
          |slave|agent (please use https://issues.jenkins.io/browse/JENKINS-42816 )|
          |whitelist|allowlist|
          |blacklist|denylist|

          If you are working on slave/agent replacement please use https://issues.jenkins.io/browse/JENKINS-42816
          A. Jard made changes -
          Summary Original: Terminology update for master, slave, whitelist, blacklist New: Terminology update for master, whitelist, blacklist

          A. Jard added a comment -

          I have updated the description with a link to Agent renaming Epic, I hope it fits all needs

          A. Jard added a comment - I have updated the description with a link to Agent renaming Epic, I hope it fits all needs
          Daniel Beck made changes -
          Description Original: In July 2020 we  [adopted|https://cd.foundation/blog/2020/08/25/jenkins-terminology-changes/] the "controller" term instead of "master", and deprecated the "whitelist/blacklist" terms. There are many places where the old terminology still needs to be replaced.

          For example, deprecated term can be:
           * in UI files, like *.jelly, *.groovy, *.html
           * in logs that ends up in job console, or Jenkins console
           * in cli output
           * HTTP API
           * Documentation, README, code comments

          Changing master in other context (like git or any scm master branch) is out of scope of this Epic.
           We invite contributors to join us and participate in cleaning up Jenkins documentation, Web and CLI interfaces, and the codebase.

          ||Deprecated term||To be replaced by||
          |master|controller|
          |slave|agent (please use https://issues.jenkins.io/browse/JENKINS-42816 )|
          |whitelist|allowlist|
          |blacklist|denylist|

          If you are working on slave/agent replacement please use https://issues.jenkins.io/browse/JENKINS-42816
          New: In July 2020 we  [adopted|https://cd.foundation/blog/2020/08/25/jenkins-terminology-changes/] the "controller" term instead of "master", and deprecated the "whitelist/blacklist" terms. There are many places where the old terminology still needs to be replaced.

          For example, deprecated term can be:
           * in UI files, like *.jelly, *.groovy, *.html
           * in logs that ends up in job console, or Jenkins console
           * in cli output
           * HTTP API
           * Documentation, README, code comments

          Changing master in other context (like git or any scm master branch) is out of scope of this Epic.
           We invite contributors to join us and participate in cleaning up Jenkins documentation, Web and CLI interfaces, and the codebase.
          ||Deprecated term||To be replaced by||
          |master|TBD (for built-in node/label) and controller (for everything else)|
          |slave|agent (please use https://issues.jenkins.io/browse/JENKINS-42816 )|
          |whitelist|allowlist|
          |blacklist|denylist|

          If you are working on slave/agent replacement please use https://issues.jenkins.io/browse/JENKINS-42816

            Unassigned Unassigned
            ajard A. Jard
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: