On 11/14/15, Michael Wiles <[email protected]> wrote: > On Fri, 13 Nov 2015, 20:16 Taher Furniturewala <[email protected]> > wrote: > >> >> Am in the process of configuring a replacement( upgraded) Jenkins master >> for an existing one . >> >> On the new master , I want the same plugins which are there on the >> current >> one ( The versions of course would be different ie whatever is the latest >> ) >> [...] >> >> Am contemplating if I copy over the old plugins directory contents onto >> the new server and restart and then choose the new versions available , >> would that work smoothly and be a better way to do it ? >> >> Is there any other simplified way to do this ? >> > > Take a look at the file system for the origin jenkins... I'm fairly > confident you'll see the hpi (jenkins plugin package) files there. > > I'm not 100% sure but if you copy those files to the same location on the > new jenkins and restart that should work... > [...]
I'd like to follow with a (somehow) different (but related) question . Is there any way to automate such things (e.g. server installations / migrations , plugin installs , build job config , ...) using Ansible [1]_ or any other equivalent tool ? .. [1] http://www.ansible.com -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Brython committer http://brython.info http://github.com/brython-dev/brython Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- 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/CAGMZAuP4jcCGodsu7oDhKS_jEo-04QH%3D6RX%2BP78oeWhYiSehpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
