Having real problem importing a job config.xml from another Jenkins server

[michael....@cisco.com]

I am having problems importing a job config.xml from another Jenkins server.  I don't have access to the other Jenkins server so I can not use the URL to import the job.  I have tried creating a new Job in jenkins and then replacing the config.xml with the one from the other server.  As soon as I select "Reload Configuration from Disk" the new job disappears.  I have also tried using the commandline: java -jar /home/saba/jenkins-cli.jar -s http://saba-ci.us.nds create-job Mike-Nam2 < /home/saba/config_NAM_IPAD-RELEASES.xml.

 

Any ideas?

[k.thi...@comcast.net]

It is possible that plugin versions or the version of Jenkins is not the same as the other server and a configuration setting is causing a problem with it being displayed.

 

Are you using promotions?

---

--
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[michael....@cisco.com]

Any idea how to get around this, if I don't have access to the other Jenkins server?

 

Thanks,

Michael

[James Nord (jnord)]

Hi Michael,

 

If you check the target server logs you will probably see an xstream exception which may give you a clue.

Once you have that clue try upgrading that plugin (rinse & repeat).

 

Just hope it’s not a jenkins version issue as then you will have to upgrade your Jenkins…

 

/James

[Slide]

Check the jenkins log, it should have messages about why it couldn't load the job and give you clues on what you might need to change.

--
Website: http://earl-of-code.com

[k.thi...@comcast.net]

Well, you would first have to figure out which section of the configuration is causing the problem.  Each configuration section is in its own tag in the config, so you should be able to just remove certain sections to find the cause.  Once you find it, it might just be updating a plugin, or updating Jenkins...or if its a bug, rolling bag a plugin or Jenkins.

 

Make sure to back up your config before editing it

[michael....@cisco.com]

Fixed the problem, the problem was an entry in the xml file, once I removed the entry it imported.

<allowEmptyArchive>false</allowEmptyArchive>

On Tuesday, June 11, 2013 9:00:12 AM UTC-7, michael....@cisco.com wrote: