You can export any job's config.xml using the Jenkins CLI (possibly via the built-in SSH server on port 2222), like so:
ssh -p 2222 <user>@<your old jenkins> get-job <job path> >config.xml
and re-import like so:
cat config.xml|ssh -p 2222 <user>@<your new jenkins> create-job <job path>
or, w/o storing the config.xml anywhere:
ssh -p 2222 <user>@<your old jenkins> get-job <job path>|ssh -p 2222 <user>@<your new jenkins> create-job
<job path>
You can get help by issuing a "help" command (ssh ... help).
Alternatively, if you want to keep the history and archived artifacts of your jobs, just rsync the ${JENKINS_HOME}/jobs folder over. Anyway, you might need to create other resources used by your jobs first, like credentials and such. In this case, the
Jenkins Configuration as Code plugin should help.
HTH...
Dirk
--
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten
Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.