Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Tagging Roles #26

Open
kameshsampath opened this issue May 9, 2016 · 2 comments
Open

Tagging Roles #26

kameshsampath opened this issue May 9, 2016 · 2 comments

Comments

@kameshsampath
Copy link
Contributor

Tagging of roles, which will allow galaxy to publish the same as versions of the roles via galaxy

@sherl0cks
Copy link
Contributor

Could you provide an example or a link @kameshsampath ? Not sure I follow what you are asking

@kameshsampath
Copy link
Contributor Author

@sherl0cks, i meant [Download Multiple Roles](https://galaxy.ansible.com/intro#Download Multiple Roles), we need to start tagging the commits on our rhtconsulting/jboss_* to make them listed as versions in galaxy roles, right now if you see the Galaxy role info via galaxy.ansible.com you see no version info available, once we start tagging our commits you will see the versions coming/listed there, then the users can choose the role_name, version kind of pattern to get the needed version of the role.

e.g. lets say we tag the current commit as 6.4.7, so the users in the roles.txt can use something like
rhtconsulting.jboss_eap,v6.4.7, and tomorrow we do update our roles for 7.0.0 then we will tag that commit as 7.0.0 and users needed EAP 7 could do rhtconsulting.jboss_eap,v7.0.0

if you already have plans to deal this kind of requirements and triaged for now then we are good.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants