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

Rename master/slave to manager/worker

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • All

      How receptive would the jenkins community be to replacing the master/slave terminology? Django and drupal have already made such a switch – https://github.com/django/django/pull/2692, https://www.drupal.org/node/2275877 – and I think their reasoning applies to Jenkins as well.

      (One could bikeshed indefinitely on replacement terms, and I'm not wedded to manager/worker in any way.)

      Changing the code is probably the easier part (though not trivial); there's also lots of documentation that would need to change, not all of it written/maintained by the jenkins project. I think the proejct is worth it even if there is a long tail of references to master/slave references that stick around in docs.

          [JENKINS-29522] Rename master/slave to manager/worker

          Craig Silverstein created issue -
          Daniel Beck made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue duplicates JENKINS-27268 [ JENKINS-27268 ]
          Kohsuke Kawaguchi made changes -
          Link New: This issue is related to JENKINS-31095 [ JENKINS-31095 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164399 ] New: JNJira + In-Review [ 197493 ]
          Craig Silverstein made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            csilvers Craig Silverstein
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: