Hi, You can use Puppet, Chef and Ansible in order to configure your Infrastructure and also your Jenkins configuration.
1) Chef recipe has been there longer than the Puppet one, and it does provide slaves auto provisioning for JNLP/ssh/swarm, Puppet module only supports swarm by default, although you can code your own module to use ssh connections. Ansible playbook no idea yet! 2) Both of them use jobs templating, but in that case I will run away of that strategy and use the Configuration as Code paradigm (called Pipeline/Workflow as Code too), either using JobDSL or Workflow plugins or Jenkins Builder in order to use the Dev best practices in the Jobs setup 3) Plugins installation and configuration are fully supported 4) Some pieces of the Jenkins global setup cannot be automated via those modules/recipes/playbooks but you can easily run some groovy script to configure them accordingly, and they support groovy scripts themselves. * Further details:* - *Puppet*: https://forge.puppetlabs.com/rtyler/jenkins It's maintained by the Jenkins community and driven by RTyler! - *Chef*: https://supermarket.chef.io/cookbooks/jenkins (It has been developed by an awesome Ruby engineer ;) - *Ansible*: https://github.com/geerlingguy/ansible-role-jenkins (It has been developed by an Evangelist of Ansible ;) - https://groups.google.com/forum/#!searchin/jenkinsci-users/puppet%7Csort:date/jenkinsci-users/lPz5oYtyudA/wsvnUDBeBgAJ I hope it helps On Saturday, 14 November 2015 16:28:32 UTC+1, Olemis Lang wrote: > > On 11/14/15, Michael Wiles <[email protected] <javascript:>> wrote: > > On Fri, 13 Nov 2015, 20:16 Taher Furniturewala <[email protected] > <javascript:>> > > 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/999c87e4-4c79-45e1-bfa4-3c29327e344f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
