ConfigFiles 3.0 appears to be mangling config.xml

[Michael Weigle]

Upgraded from 2.18 to 3.0

After the upgrade, configs persist on the filesystem inside config.xml until that job is visited in the UI (presumably, config.xml is revalidated at that point and 3.0 throws the error). The attached unreadable_data message also appears in the Manage Old Data section.

Old config.xml shows this comparator: <comparator class="org.jenkinsci.plugins.configfiles.folder.FolderConfigFileProperty$1"/>
New config.xml shows this comparator: <comparator class="org.jenkinsci.plugins.configfiles.ConfigComparator"/>

I see some commits about pulling ConfigComparator out from where it used to live, but I'm not sure if that's the exact cause of what's going on here.

Thanks,

Mike

[Benjamin Brummer]

I also had to reconfigure one jenkins job, after this update. Configuration was gone almost completely. All provided maven settings.xml files where gone and but i could set them up again with identical id's.

[Björn Pedersen]

Just for reference:A jira issue exists: https://issues.jenkins-ci.org/browse/JENKINS-53399