Deployment/publishing workflow to Galaxy
Opened this issue · 2 comments
Thulium-Drake commented
Investigate a means to auto-publish any new versions that are tagged to Ansible Galaxy.
dmsimard commented
This is already automated with Zuul and is how most of the community collections are published, i.e: https://dashboard.zuul.ansible.com/t/ansible/builds?job_name=release-ansible-collection-galaxy&pipeline=release
It triggers when pushing a tag to the repository, takes care of building the collection and then publishing it.
We would probably have to supply our own credentials since we're not in the community. namespace but it should be possible to use it.
amilcarlucas commented
Will there be a new collection version once you release ara 1.6.0 ?
I need ara_record FQCN in order to fix ansible-lint errors :(