Copying JENKINS_HOME was how I moved from one server to another. It worked great for me. Just want to make sure you initially install the same version of Jenkins on the destination server during migration to avoid any weird issues. Then update the Jenkins URL in the global config and you should be off and running.
--
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/2ec577ff-fcbd-4c48-871e-97e880b7df65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
One small quick tip about migrating big instances: we needed to move a Jenkins master (~1000 jobs) to a new machine minimizing the downtime.
* leave the running server as is
* provision the new machine and sync as often as you want the .jenkins directory from the running machine to that new one (rsync in mirror + --delete mode)
* plan migration
* sync a pre-last time
* shutdown
* last sync (supposedly very small diff)
* start the new server
(Sure you'll want to do some checks on the new servers that Jenkins can indeed run fine before the real migration)
We used the same technique to move a ~300GB nexus server without any issue.
My 2 cents
HTH
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc8ju93H_jGBECb1_P6EPUzzQGrB-f%3DJRGdMxcNgrzCJw%40mail.gmail.com.