Hi Ryan, There are different solutions besides of using Docker (which IMO, it's the one of the best ones as Mark already suggested), as long as you use Configuration Management tools: - Ansible -> https://galaxy.ansible.com/geerlingguy/jenkins/ - Puppet -> https://forge.puppet.com/rtyler/jenkins - Chef -> https://supermarket.chef.io/cookbooks/jenkins - Salt -> https://github.com/saltstack-formulas/jenkins-formula
Besides of that, you can automate even more if you use the https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Hook+Script , I've used to configured for instance: some active directory, security policies, ant/jdk/maven installations, ssh/other credentials and so on. Cheers On Thursday, 13 October 2016 18:15:53 UTC+1, Mark Waite wrote: > > The official Jenkins image can be easily extended to pass in the > configuration in files. That's how it is designed to work, and it has > worked quite well for me. > > If you'd like to see one way to do it, look at the lts-with-plugins branch > of my docker repo, > https://github.com/MarkEWaite/docker/tree/lts-with-plugins . I've also > added credentials and agents and many other configuration settings by > committing files to a private repository similar to that one. I use > docker images to test the Jenkins git plugin and the Jenkins git client > plugin and have been very pleased with how well Jenkins works with complex > setups in a docker environment. > > I'm sure there are others with much better techniques than mine, but > you're welcome to refer to my techniques as one way of doing it. > > Mark Waite > > On Thu, Oct 13, 2016 at 9:54 AM Ryan Cocks <[email protected] > <javascript:>> wrote: > >> Hi, >> >> I'm a bit surprised to find Jenkins installation requires manual >> intervention via a user interface. >> >> Are there any guides on how to avoid the UI and do an automated deploy of >> Jenkins itself? >> >> Best idea I have is to store a post-setup jenkins docker image. I'd much >> prefer to be able to pass in the configuration in files or the environment. >> >> Best regards, >> Ryan >> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/3fabfeff-5336-45dc-a3ea-0f2a271d4a11%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/3fabfeff-5336-45dc-a3ea-0f2a271d4a11%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/89e03e52-27fd-4dc9-87e9-3e34e10d5ab4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
