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

Rename master/slave to manager/worker


    • 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.

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