On Wed, Nov 8, 2017 at 3:42 PM, Greg Sutcliffe <[email protected]> wrote:
> On 08/11/17 12:35, 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. > > +1 from me, its very hard to discover today. > +1 anything that makes it easier for a developer to understand the CI infra better is a plus :) > > Greg > > -- > 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. > -- 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.
