Aggregating jobs and config from many servers into one

[Kevin White]

My team has several different Jenkins servers that we have decided to aggregate into just one.  I'm somewhat familiar with the process of migrating one old Jenkins instance to a new one, where the new one is essentially a clone of the old.  What I haven't seen is instructions for combining jobs/configs/plugins from multiple instances into one.

I have installed the Job Import plugin, but for some reason, it doesn't list the jobs on most of the remote machines so they can't be imported.  No errors, just no jobs listing.  I suspect it may have something to do with the fact that the remote machines all use SSL.  I have provided working credentials in the plugin configuration for each of the remote instances, so that's not the issue.

I have looked at thinBackup plugin, but it appears that it will restore only from one source, not many.

If I copy the jobs folder over from the remotes, I won't get all the necessary plugins and other configuration files.

I am currently trying to rsync from each of the remotes to the new one, but I have a feeling that will result in some incompatibilities.

Any suggestions on how best to accomplish this?

[RAJENDRA PRASAD]

Check whether the remote machines enabled REST Interface or jenkins cli, you can easily export and import  jobs from any jenkins server to any other jenkins server, other useful utility also I found called 'butler, script, check online if you cannot find it I can send you link for the that to download and use it, it is very simple, it also supports export and importing plugins too.

Thanks ,

rajendra....@gmail.com

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d88f55f3-4712-4e47-9f50-930a1f7dc207%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kevin White]

Thanks Rajendra.  I had avoided using the CLI because there are so many jobs to be moved, and it doesn't move plugins, credentials, etc.  I was hoping for a more-automated way of doing it, but it might not exist.  I have looked at butler, I'll take another look.

[RAJENDRA PRASAD]

Another simple way is to just copy every job config.xml file from source jenkins server to target jenkins server. You can use shell script for that. Just copy <jenkins_hime>/jobs/<jobname-name-folder>/config.xml from source jenkins folder to target jenkins server folder.

Jenkins cli is not a bad option, if we can script property we can move plugins and jobs easily.

Rajendra

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6f36556d-677f-4b89-b4bf-5a4e1451d870%40googlegroups.com.

[Baptiste Mathus]

I would /simply/ move everything under a different folder locally. Then copy everything to a central new instance using rsync or something like this, then everything looks fine.

If it does, you'll then be able to use the folders plugin to move things where you want them.

My 2 cents

--