On Mar 10, 2017, at 6:36 PM, Shameera Rathnayaka 
<shameerai...@gmail.com<mailto:shameerai...@gmail.com>> wrote:

Hi,

I second Marlon's point about burden on CI/CD by having totally two 
repositories, also we should have good discipline to keep two separate repos in 
sync which is kind of hard IMO. Moving all scripts to one place and organizing 
them in different subdirectories make more sense. That is why I created 
dev-tools and dev-tools/ansible in the first place.

Hey Shameera,

Yeah, I agree. This was also my concern and I now think the advantage is with 
keeping the scripts in the same repo.

This makes me think that the PGA Ansible scripts should really be in the PGA 
repo.


We only need to maintain two different scripts, one for development and one for 
master, that is the only thing we will officially maintain.(feature developers 
can have their own variation of scripts, that is not our concern). We need to 
have proper code review sessions to avoid our scripts being obsolete. As all in 
one repo help us to do this in same PR. We can tag dev-tools along with new 
release branch to have proper versioning.


Regarding scripts becoming obsolete, I would like to see us using these scripts 
as part of CI/CD eventually, so that any breakage is immediately obvious.

Thanks,

Marcus

Reply via email to