jenkinsci / jenkinsci/ec2-plugin

[JENKINS-63660] [ec2-plugin] Slave to agent term sweep

Open
#1,791 2 comments 0 reactions 0 assignees View on GitHub
agent component:ec2-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
292
Forks
709
Avg merge
3d 16h
Merged PRs (30d)
4

Description

As of Jenkins core has been changing the terminology from "Slave" to "Agent", and plugins should follow this, I create this ticket to rename the "Slave" references on the ec2-plugin to "Agent".

Acceptance Criteria:



  • There are no "Slave" references on source code

  • There are no "Slave" references on documentation

We could still keep a link in the documentation to this ticket or the EPIC so people looking for the term "Slave" can find that in the future just in case they have no idea about this renaming.

---
Originally reported by froblesmartin, imported from: [ec2-plugin] Slave to agent term sweep


  • assignee: thoulen
  • status: Open
  • priority: Minor
  • component(s): ec2-plugin
  • label(s): plugin, slave, terminology
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-06

Raw content of original issue

As of Jenkins core has been changing the terminology from "Slave" to "Agent", and plugins should follow this, I create this ticket to rename the "Slave" references on the ec2-plugin to "Agent".

Acceptance Criteria:



  • There are no "Slave" references on source code

  • There are no "Slave" references on documentation

We could still keep a link in the documentation to this ticket or the EPIC so people looking for the term "Slave" can find that in the future just in case they have no idea about this renaming.

Contributor guide

Open the contributing guide

Research direction

The issue names no files or tests; start with a repository-wide search for "Slave" across source code and documentation. Done means the remaining references are removed or intentionally linked to the issue or epic, as described in the acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.