Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop support for remoting releases before 2024-08 #9569

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

daniel-beck
Copy link
Member

@daniel-beck daniel-beck commented Aug 7, 2024

The fix for SECURITY-3430 retains compatibility with older remoting releases to have a smoother upgrade experience. This PR drops that support. It's probably going to be a while before we want to merge this, but I thought it would be useful to have this prepared.

Testing done

Autotests

Proposed changelog entries

  • Drop support for Remoting (agent.jar) releases from before August 2024.

Proposed upgrade guidelines

(Copied from #9440 for consistency)

Increase the minimum required Remoting version to 3256.3258.v858f3c9a_f69d (released on August 7, 2024). When an agent with a Remoting version older than 3256.3258.v858f3c9a_f69d connects to the Jenkins controller, the agent connection is rejected. Ensure that all agents are running a recent version of Remoting prior to upgrading. Agents with unsupported Remoting versions can be allowed to connect to the controller by setting the hudson.slaves.SlaveComputer.allowUnsupportedRemotingVersions system property to true.

Submitter checklist

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 7, 2024
Copy link
Contributor

github-actions bot commented Aug 7, 2024

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot removed the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 14, 2024
@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 25, 2024
Copy link
Contributor

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot removed the unresolved-merge-conflict There is a merge conflict with the target branch. label Aug 26, 2024
@github-actions github-actions bot added the unresolved-merge-conflict There is a merge conflict with the target branch. label Sep 16, 2024
Copy link
Contributor

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions github-actions bot added unresolved-merge-conflict There is a merge conflict with the target branch. and removed unresolved-merge-conflict There is a merge conflict with the target branch. labels Sep 16, 2024
Copy link
Contributor

Please take a moment and address the merge conflicts of your pull request. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unresolved-merge-conflict There is a merge conflict with the target branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant