On Wed, 2017-11-08 at 07:35 -0500, Eric D Helms wrote: > All, > > I brought this idea up in a separate thread, but want to formalize it into > it's own direct > proposal. As of today, the Jenkins Job (JJB) configurations live buried > inside the foreman-infra > repository. I believe this makes them hard to discover [1] and awkward to > work with being inside a > puppet module. My proposal is: > > 1) Create foreman-ci github repository > 2) Move everything under [1] to foreman-ci > 3) Update the jenkins_job_builder puppet_module to clone this new repository > > Further, I think this will allow CI focused work to happen and be separate > from the maintenance of > our community infrastructure. > > > Eric > > [1] > https://github.com/theforeman/foreman-infra/tree/master/puppet/modules/jenkins_job_builder/fil > es/theforeman.org >
We do something similar in upstream Pulp today with our jekins job templates, and it has worked out really well for us. It sounds like a good idea. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: This is a digitally signed message part
