Hi Jeremy and Brian, I'm looking into a similar set up however, what we'd like to do is have a repo per Ansible Role (eg apache, php, tomcat, java) so we can be working on different roles at the same time without git conflicts being thrown at us. Right now what we have is one repo with all of our roles in one repo and multiple people working on different roles. We would also like to be able to tag each role with different versions of the role. The problem right now is that if we want to assemble an Ansible package with a combination of these roles and their version numbers, we are unable to do that. We are not using Ansible Tower. Any suggestions?
Best, Jeff On Friday, August 21, 2015 at 1:42:40 PM UTC-4, Jeremy wrote: > > Thanks for the quick feedback. We may start moving forward with this > shortly. Hopefully I'll have some lessons learned that I can share later. > > On Friday, August 21, 2015 at 10:09:00 AM UTC-4, Brian Coca wrote: >> >> It is not hard, it is easier if you have a convention on the playbook >> names (build.yml, deploy.yml), then you just need a list of the apps >> and their repo locations: >> >> apps: >> - app1: git://internal/repo/app1.git >> >> >> and a playbook that goes over this list, checks out all the apps and >> then runs build.yml and deploy.yml for each. >> >> >> If you don't standardize the names, add them to the vars file above: >> >> apps: >> app1: >> src: git://internal/repo/app1.git >> build: make.yml >> deploy: push.yml >> >> -- >> Brian Coca >> > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/dcc25265-6292-40ec-b60c-80146501abe5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
