-
Epic
-
Resolution: Fixed
-
Major
-
Cleanup anonymous class usages for Remoting in Jenkins Core, Remoting and Modules
-
-
Remoting 3.28
After adding extra diagnostics for cases like JENKINS-49795, there will be warning reports about anonymous classes being serialized over Remoting. Somebody needs to cleanup these usages.
Examples:
- relates to
-
JENKINS-49795 Bad serialization of ParametersAction.parameterDefinitionNames
-
- Resolved
-
[JENKINS-49987] Cleanup anonymous class usages for Remoting in Jenkins Core, Remoting and Modules
Link |
New:
This issue relates to |
Description |
New:
After adding extra diagnostics for cases like Examples: * https://github.com/jenkinsci/jenkins/search?utf8=%E2%9C%93&q=%22new+MasterToSlaveCallable%22&type= * https://github.com/jenkinsci/remoting/blob/9b8fd56e780f0c042c8ac35333e87faba8c5f81f/src/main/java/hudson/remoting/forward/PortForwarder.java#L135 * ... |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Labels | New: diagnostics serialization |
Epic Child |
New:
|
Comment | [ Note that currently the diagnostic lives in {{ClassFilterImpl}} in core, so it will apply to all XStream usages, but only to _inbound_ Remoting commands. Probably it should be moved to {{ClassFilter.STANDARD}} so that we would find instances of the much more common case of _outbound_ Remoting callables using anonymous inner classes. ] |
Assignee | New: Jeff Thompson [ jthompson ] |
Released As | New: Remoting 3.28 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |