"slave" has been deprecated terminology since Jenkins 2

[rtyler]

I noticed in the examples in the readme this snippet:

jenkins:
  securityRealm:
    (...)

  nodes:
    slave:
      name: "static-slave"
      remoteFS: "/home/jenkins"
      launcher: "jnlp"

Since this is early in the project, can usage of "slave" be replaced with "agent" in the API to match the existing terminology used since Jenkins 2.0?

It would be a big step backwards for such an important project to adopt the term.

[daniel-beck]

Pretty sure I brought up the need for synonym/alternative term support with @ndeloof because of this. UI labels are often not what the internal class names are.

[oleg-nenashev]

yup, it needs to be cleaned up.
FTR https://issues.jenkins-ci.org/browse/JENKINS-42816

[ndeloof]

@daniel-beck has to be fixed here : https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/DumbSlave.java#L68

[oleg-nenashev]

Oh, these symbols are brilliant

[oleg-nenashev]

@ndeloof Could you please create a ticket and add it to the https://issues.jenkins-ci.org/browse/JENKINS-42816 EPIC?

[oleg-nenashev]

The core's fix has been integrated towards 2.109, JENKINS-49661 is a tracking number

[AnneTheAgile]

once core fix is done, then in this repo do we only need to change the doc strings 'slave' to 'agent' found via ; https://github.com/jenkinsci/configuration-as-code-plugin/search?utf8=%E2%9C%93&q=slave&type= ?

[ndeloof]

plugin only reflect Java model and Symbol annotations it uses. We have no direct reference to "slave"