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

Fix issue with TeeStep and remoting #251

Merged
merged 1 commit into from
Jun 24, 2024
Merged

Conversation

slide
Copy link
Member

@slide slide commented Mar 28, 2024

According to the jenkins doc about Using anonymous classes in remoting (https://www.jenkins.io/doc/developer/extensibility/serialization-of-anonymous-classes/#usages-in-remoting), it is better to use a private static class, as anonymous classes sometimes have issues being sent across remoting. This changes the anonymous class to a private static class so the TeeStep works correctly across remoting channels.

Testing done

Ran the full test suite as well as installing on a test server and running several workloads.

Submitter checklist

Preview Give feedback

According to the jenkins doc about Using anonymous classes in remoting
(https://www.jenkins.io/doc/developer/extensibility/serialization-of-anonymous-classes/#usages-in-remoting),
it is better to use a private static class, as anonymous classes
sometimes have issues being sent across remoting. This changes the
anonymous class to a private static class so the TeeStep works
correctly across remoting channels.
@slide slide requested a review from a team as a code owner March 28, 2024 19:16
@rsandell rsandell added the bug label Jun 24, 2024
@rsandell rsandell merged commit 12a1522 into jenkinsci:master Jun 24, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants