You could also go the other way around and use whatever configuration management tool you use (like puppet) to provision your jenkins instances.
On Wed, Feb 6, 2013 at 3:21 PM, William Soula <william.so...@drillinginfo.com> wrote: > Also can look into Jenkins Job Builder to put your job configuration under > version control. And I second the cli for plugin loading, can load them all > with one command you could put in version control. Then you just need the > war and the global config. > > https://github.com/openstack-infra/jenkins-job-builder > > Will > ________________________________________ > From: jenkinsci-users@googlegroups.com [jenkinsci-users@googlegroups.com] on > behalf of Sami Tikka [sjti...@gmail.com] > Sent: Wednesday, February 06, 2013 3:16 PM > To: jenkinsci-users@googlegroups.com > Subject: Re: Beta Build Environment > > I have developed instructions on how to set up Jenkins from scratch if our > Jenkins would catch fire and burn to the ground. > > I have also used the instructions to set up a 2nd Jenkins to run a newer > version of Jenkins before upgrading. > > You need the jenkins.war, the plugins, the global config.xml and config.xml > files for every job. If you want to try your hand at automating, remember > that the Jenkins cli can be used to upload plugins and job configurations. > > -- Sami > > "Mandeville, Rob" <rmandevi...@litle.com> kirjoitti 5.2.2013 kello 21.09: > >> I work for an agile development group, so we like to test everything, >> including our build environment. I have been challenged to figure out how >> my team can create a second build environment to test enhancements on. This >> would also involve creating a beta copy of our Jenkins instance. >> >> We need to be able to test changes to (in order of importance) job >> configurations, slave configurations, and (possibly) plugin configurations. >> Is there any way to do this? Has anyone ever tried? >> >> Thanks in advance, >> >> --Rob Mandeville >> The information in this message is for the intended recipient(s) only and >> may be the proprietary and/or confidential property of Litle & Co., LLC, and >> thus protected from disclosure. If you are not the intended recipient(s), or >> an employee or agent responsible for delivering this message to the intended >> recipient, you are hereby notified that any use, dissemination, distribution >> or copying of this communication is prohibited. If you have received this >> communication in error, please notify Litle & Co. immediately by replying to >> this message and then promptly deleting it and your reply permanently from >> your computer. >> >> -- >> 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-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > -- > 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-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > 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-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- Andrew Melo -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
