On Thu, Nov 9, 2017 at 9:46 AM, Ewoud Kohl van Wijngaarden < [email protected]> wrote:
> On Thu, Nov 09, 2017 at 02:37:10PM +0000, Greg Sutcliffe wrote: > >> On 09/11/17 14:25, Ewoud Kohl van Wijngaarden wrote: >> >>> If a separate repository, would it not be as simple as adding a git >>>> clone? >>>> >>> >>> Possibly, I don't have that much insight into the entire deployment >>> flow. Hence my preference of making small changes since our backlog is >>> big enough already. Of course if you're willing to take it on then be my >>> guest. >>> >> >> Currently it's a Jenkins Job [1] that notices a change in the upstream >> repo, and deploys it to the puppetmaster. Should be trivial enough to >> make the changes you want there - adding a git submodule to the infra >> repo might "just work", looking at it. >> >> [1] http://ci.theforeman.org/job/deploy_puppet/ >> > > A git submodule might work - we wouldn't get automatic updates thus > doubling the work though. If you mean adding a separate repository to the > config then that could work well. Another option is we just move this out of puppet all together and a have a job that runs JJB whenever the repository updates to update the jobs (job-ception). > > > -- > 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.
