On 12/24/2017 12:05 AM, Lupin Deterd wrote:
> This works initially when it was only one team doing the work/changes
> but after opening the work to other teams (apps) it becomes unwieldy.
> The pain point happens in #2, #3 where some changes have to wait for a
> schedule before it's get promoted
Hi,
What is the work-flow of you Control-repo? We are using single repo with
multiple(DEV, QA, PROD) branches which r10k map to Puppet environment.
Below is our workflow process:
1) A team member creates a feature branch from Prod.
2) After completing their changes they will then merge it into D
