Status: Resolved (View Workflow)
JENKINS-49573 comment conversation)
After upgrading to Jenkins 2.110 and actually presumably
JENKINS-49795 I saw the following warning logs:
2018-03-07 11:39:38 WARNING [jenkins.security.ClassFilterImpl lambda$isBlacklisted$1] JENKINS-49573: attempt to (de-)serialize anonymous class hudson.model.ParametersDefinitionProperty$1 in file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.110.jar
JENKINS-50457 Attempt to (de-)serialize anonymous class
- relates to
JENKINS-49795 Bad serialization of ParametersAction.parameterDefinitionNames
Jenkins 2.110+ will no longer save this class name for new builds. Historical build records may continue to refer to it. I suppose ParametersAction.readResolve could replace the list with an ArrayList but this does not suffice to trigger a resave; Jenkins currently offers no API for an object’s readResolve to request a save of the top-level object being loaded from XmlFile.
Just a warning; probably could be closed as Won’t Fix.
And not a JEP-200 issue per se.
JENKINS-49705 was a robustness improvement merely inspired by debugging a JEP-200 regression.
Since I still get this warning:
2018-04-04 12:26:59 WARNING [org.jenkinsci.remoting.util.AnonymousClassWarnings warn] Attempt to (de-)serialize anonymous class hudson.model.ParametersDefinitionProperty$1 in file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.114.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
Is that OK?
Or when is it still expected to pop up (e.g. solely due to looking at pipeline job in classic UI via stage view for instance)?
(Updating cloned issue, maybe I should not have used cloning in the first place?)