Hi! We are running Jenkins in Docker containers (as for ourselves as for our customers) for a quite some time already and using the possibility to run Groovy scripts on startup provided by Cloudbees Jenkins Docker image to handle global/security/slaves. Over time we started to accumulate those scripts and even moved configuration part to properties files. You can see scripts and property files here
https://github.com/Praqma/JenkinsAsCodeReference/tree/master/dockerizeit/master So far we were using this repository https://github.com/Praqma/JenkinsAsCodeReference as a template. Every time we are about to set up new Jenkins master we would do a copy/fork, modify property files, modify plugins.txt and we are ready to go. Everything is handled as code under version control. What else to wish? We are planning to put more effort into those scripts - decouple them from properties, i.e. separate what from how so we have scripts in one place instead of scatted around all copies that need to be maintained. Before we do so I wanted to check if there is any work ongoing or being planned to implement Jenkins global/security/slaves configuration as code? If it is then we would love to collaborate and join forces Bobby, you mentioned that you know someone who is looking into the same issue. Could you please share this post so we can get a discussion started? BR, Andrey -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a78c9f08-197e-4e80-8dc5-cbf67ebd6f76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
