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

[JENKINS-47896] SerializableOnlyOverRemoting #3980

Conversation

jglick
Copy link
Member

@jglick jglick commented Apr 11, 2019

#3144 with a merge conflict resolved and a minor fixup. See jenkinsci/remoting#206 for background.

Proposed Changelog

  • RFE (internal), Prevent occasional serialization of Remoting classes to a wrong channel

oleg-nenashev and others added 8 commits November 16, 2017 10:53
Due to the implementation specifics, some classes in the core are serializable only over Remoting.
This change just marks these classes and utilizes the convenience method in the interface for serialization/deserialization operations.
… of github.com:oleg-nenashev/jenkins into SerializableOnlyOverRemoting-JENKINS-47896
@jglick jglick added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Apr 19, 2019
@daniel-beck
Copy link
Member

Someone else needs to write a changelog for this.

@jglick
Copy link
Member Author

jglick commented Apr 19, 2019

No changelog is needed here.

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be OK if I recall the change correctly

@@ -1828,7 +1830,7 @@ void skip0() {
/**
* Represents a process tree over a channel.
*/
public static class Remote extends ProcessTree implements Serializable {
public static class Remote extends ProcessTree {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could it be a breaking change? I know it comes from #3144 , but I am not sure why I did that

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This implements Serializable clause was always redundant, given the superclass:

public abstract class ProcessTree implements Iterable<OSProcess>, IProcessTree, Serializable

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. One month without coding for me :D

@oleg-nenashev
Copy link
Member

@daniel-beck added some changelog summary just in case you still expect it

@oleg-nenashev oleg-nenashev merged commit e2da5e4 into jenkinsci:master Apr 25, 2019
@jglick jglick deleted the SerializableOnlyOverRemoting-JENKINS-47896 branch April 25, 2019 15:03
@oleg-nenashev
Copy link
Member

FYI https://issues.jenkins-ci.org/browse/JENKINS-57229 is most likely caused by this PR

@oleg-nenashev
Copy link
Member

Also Maven Plugin and SCoverage according to https://issues.jenkins-ci.org/browse/JENKINS-57244 . So we have 4 plugins which misuse serialization

The proposed plan is to...

  • Disable the serialization failure by default
  • Add Telemetry as @daniel-beck suggests + Add system logging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants