If we end up creating a whole new architecture in parallel of the current one, we will need a Jenkins server and have its configuration fully in puppet. Following a meeting on April 3rd with Chase/AndrewB. , Antoine should figure out how OpenStack handle their 8+ Jenkins config.
|Declined||None||T69027 Jenkins: Figure out a long term solution to maintaining Jenkins configuration|
|Resolved||• hashar||T95049 Figure out how Jenkins conf is maintained by OpenStack|
OpenStack has a fully puppetized Jenkins. They have split their puppet modules as independent repositories so that people from the OpenStack community can benefit from them and thus us as well. http://git.openstack.org/cgit/openstack-infra/puppet-jenkins
The equivalent of our operations/puppet.git is openstack-infra/system-config with the equivalent of our roles in the module openstack_project.
The entry point shows they even support Jenkins plugins.
I am not sure how the Jenkins master config.xml file is generated though.
Hey @zeljkofilipin that task has some informations related to OpenStack managing their Jenkins installation via puppet. The puppet module at http://git.openstack.org/cgit/openstack-infra/puppet-jenkins does most of the work, a good inspiration.