I followed my normal procedure in updating our Jenkins builder:
- Update all Jenkins plugins first.
- Update jenkins core (using .war file)
I got the error message about JEP-200 and XStream, so I browsed to the wiki page. It had a note in there about -Dhudson.remoting.ClassFilter=, with a comma-separated list of class names from the log file. I got the list of classes:
So, I added those as a comma-separated list to -Dhudson.remoting.ClassFilter= and restarted Tomcat. Jenkins came back (authentication worked, but no build information is available, and slaves cannot connect), but I am now seeing a message about "You have data stored in an older format and/or unreadable data.". I am a bit afraid I will lose my build history and other metadata if I click on "Discard Unreadable Data". Is that a "safe" operation for my builds metadata?
Also, why do I need to add so many exclusions to the hudson.remoting.ClassFilter, some of which seem to be internal to jenkins/hudson? Shouldn't that "just work"? Did I do something wrong in the upgrade?
|Summary||JEP-200: After Jenkins update to 2.103, unable to start unless -Dhudson.remoting.ClassFilter= contains hudson.* class names||JEP-200: After Jenkins update to 2.103, unable to start unless hudson.remoting.ClassFilter contains hudson.* and jenkins.* class names|
|Priority||Minor [ 4 ]||Critical [ 2 ]|
|Assignee||Jesse Glick [ jglick ]|
|Status||In Progress [ 3 ]||Open [ 1 ]|
|Summary||JEP-200: After Jenkins update to 2.103, unable to start unless hudson.remoting.ClassFilter contains hudson.* and jenkins.* class names||JEP-200 location-based whitelisting broken in obsolete versions of Tomcat|
|Remote Link||This issue links to "PR 3264 (Web Link)" [ 19952 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Labels||JEP-200 lts-candidate||2.89.4-rejected JEP-200 lts-candidate|
|Labels||2.89.4-rejected JEP-200 lts-candidate||2.89.4-rejected JEP-200|