On Thu, Nov 9, 2017 at 9:00 AM, Ewoud Kohl van Wijngaarden < [email protected]> wrote:
> On Wed, Nov 08, 2017 at 07:35:04AM -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. >> > > +1 to making it more visible. > > I'm not sure whether a separate repo or a top level directory in > foreman-infra is best. One benefit of a single repository is that they're > somewhat tightly linked: the JJB version and the templates we use. > I don't know when you say template here. What template? > > Would a we be able to move the directory to the top level and have a > symlink at the puppet module level? If that'd work I'd prefer that as a > first step since we wouldn't have to modify our current deployment model. If a separate repository, would it not be as simple as adding a git clone? > > > Eric >> >> [1] >> https://github.com/theforeman/foreman-infra/tree/master/pupp >> et/modules/jenkins_job_builder/files/theforeman.org >> > > -- > 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. > -- Eric D. Helms Red Hat Engineering -- 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.
