Hello, Is there any more information on this? I've also just (resumed) trying to upgrade from Hudson 2.0.0 and noted that the configuration file format is * completely* different.
My existing config files have pretty much *everything*, including the build commands, defined within: <project-properties class="java.util.concurrent.ConcurrentHashMap"> In the new file format, build commands are stored under <builders>. When I cleanup unused fields from the config file it deletes just about everything, and leaves an empty skeleton of a config file. Worse still, the job is still not visible in the Jenkins UI until I manually hack the config file to include these empty elements: <publishers/> <buildWrappers/> Can somebody with better knowledge of the history of the configuration file formats weigh in with some advice on what's going on here? Is there any automated migration route? Thanks in advance, Daniel Fortunov On Wednesday, April 25, 2012 11:31:46 AM UTC+1, Marcel Schutte wrote: > > Hi, > > Does anyone have experience migrating from hudson 2.2.0 to jenkins > (current version, 1.461) ? The format of the hudson config files has > changed and migration isn't as easy as it used to be: > > - some settings aren't picked up (for instance a project specific jdk and > the schedule for 'build periodically') > - even after selecting 'upgrade' and 'discard unreadable data', I get lots > of startup errors like this: > > WARNING: Skipping a non-existent field project-properties > com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: > No such field hudson.maven.MavenModule.project-properties > > I've got 800+ jobs, so fixing them manually is not something I look > forward to :) > > Regards, > Marcel >
