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 Le 22 sept. 2015 9:49 PM, "Slide" <[email protected]> a écrit : > 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. > > On Tue, Sep 22, 2015, 12:25 Victor Martinez <[email protected]> > wrote: > >> What about using the SCM Sync plugin instead? >> - >> https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin >> >> Cheers >> >> On Tuesday, 22 September 2015 18:55:46 UTC+2, Justin wrote: >>> >>> My orgranization is moving to a new datacenter. I know that jobs can be >>> migrated between servers by just copying the job folder. But what about the >>> rest of the server instance (global credentials, global security, plugin >>> configurations, user database/settings, etc)? I've seen some older posts >>> (for hudson rather than jenkins) saying to do a fresh install and then >>> overwrite JENKINS_HOME on the new server with the install from the old >>> server. Is that still a preferred method? >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/2ec577ff-fcbd-4c48-871e-97e880b7df65%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/2ec577ff-fcbd-4c48-871e-97e880b7df65%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc8ju93H_jGBECb1_P6EPUzzQGrB-f%3DJRGdMxcNgrzCJw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVc8ju93H_jGBECb1_P6EPUzzQGrB-f%3DJRGdMxcNgrzCJw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7Je%3D3udv2a7e_6i0xdsa14SuHLbaKFo%3D7YxPL4Zi%2Bnkw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
