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.
Am Montag, 3. September 2018 20:14:28 UTC+2 schrieb 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 > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6924446a-f129-4d9b-b78a-d824a5e0f9e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
