Fix issue with TeeStep and remoting #251
Merged
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.
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