[JENKINS-63905] Agent to controller rather than agent to master #4980
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JENKINS-63905 Terminology - Agent to controller, not agent to master
Update the terminology in the agent access control subsystem so that new screenshots can be taken to insert into the jenkins.io page at https://www.jenkins.io/doc/book/managing/security/#agentmaster-access-control or can be integrated into the new page proposed in PR-3353
Tested interactively to confirm that upgrade from Jenkins 2.249.2 worked as expected and that new install also worked as expected.
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
Proposed changelog entries
section only if there are breaking changes or other changes which may require extra steps from users during the upgradeMaintainer checklist
Before the changes are marked as
ready-for-merge
:Proposed changelog entries
are correctupgrade-guide-needed
label is set and there is aProposed upgrade guidelines
section in the PR title. (example)lts-candidate
to be considered (see query).New screenshots for documentation
Enabling agent to controller access control
Define exceptions for agent to controller access