Multirepo vs. monorepo

[karras]

As discussed already we should consider moving to a multi repo setup and then publish all roles on ansible-galaxy.

Pros:

• ansible-galaxy integration
• easier integration for other projects (allows cherry picking)
• higher possibility for contributions

Cons:

• We'll need some glue code to do testing and deployments
• Some kind of versioning has to be in place and consistent, otherwise it gets messy (at the moment enforced by using HEAD)

@hairmare / @keachi please post your views as well, especially procs and cons...

Props to @hairmare for making this a hot topic! :hot_pepper:

[keachi]

:hot_pepper: you said the most pros and cons already.

Pros:

• pull requests and issues are per role and so it's easier to match
• each role gets checked in CI independently (and we can easy integrate that with a test framework)

Cons:

• more git repositories to manage
• some stuff will just be copy&paste (like Travis CI configuration)

[karras]

I think we should go for a multi repo setup but need to set some boundaries first.

• Name scheme for the repository? We should prefix the roles properly otherwise people might run into issues when every role is simply called nginx or similar. Example: ansible-adfinis-nginx or adfinis-ansible-nginx

• How will tests be defined? Galaxy creates a tests directory by default. I think we should follow that approach and have a test playbook and inventory file stored in each role repository. I'm not sure yet how to handle generic tests like linting, having to update 100 repos is not that great.

• How will the roles be versioned? I guess we'll have to use git tags, AFAIK galaxy only supports those.

• How would you use the roles? Probably using a requirements.yml file to include all necessary roles in specific versions.

• How will the roles in galaxy be updated automatically? https://docs.ansible.com/ansible/latest/galaxy.html#travis-integrations

[keachi]

• Naming: I think ansible-nginx will suffice, we don't have forked roles in this organization. On Ansible Galaxy, I think we should name them adfinis-nginx.
• The tests subdirectory is common sense and widely used, so we shouldn't do that another way. Ansible Lint shouldn't change in any way, each repository will be checked in Travis CI with Ansible Lint, that's not a big deal.
• Git tags is THE way to version git versioned code. So why should we even think about another way?
• Update the roles automatically in Galaxy shouldn't be a big deal, there are a lot of examples out in the net.

[hairmare]

I'd drop the "adfinis-" prefix as well but I'd also use "ansible-role-" as prefix so it possible to do things like "ansible-module-" or similar things at a later stage.

[karras]

Sounds good to me. Meaning the naming scheme will look like this:

GitHub:

• ansible-role-nginx
• ansible-module-ucs

Galaxy:

• adfinis-nginx
• adfinis-mysql

[karras]

Related #48

[keachi]

On Galaxy each role is named by account.role. Do we name our roles like adfinis-$ROLE or do we name our roles like $ROLE. I propose that we name our roles just $ROLE, because then the whole name will be adfinis-sygroup.$ROLE, e.g. adfinis-sygroup.nginx.

[karras]

Sounds fine to me. On GitHub:

* ansible-role-nginx
* ansible-module-ucs

On Galaxy:

* nginx (adfinis-sygroup.nginx)
* mysql (adfinis-sygroup.mysql)