Closed manics closed 4 years ago
Summarizing here an earlier investigation on pushing pre-releases to Ansible Galaxy:
1.2.0.dev1
or 1.2.dev1
will be rejected by Galaxy at import time but 1.2.0-m1
or 1.2.0-beta1
will be acceptedrequirements.yml
file that does not pin the role version, with Ansible 2.6, both ansible-galaxy install -r requirement.yml
or ansible-galaxy install <role_namespace>.<role_name>
will download the latest tag independently of whether it is a pre-release or notAs a general summary, we should avoid creating role pre-releases on Galaxy. For consuming intermediate versions, pointing at a GitHub commit is probably the most robust solution for now.
Conflicting PR. Removed from build ANSIBLE-ROLES-merge#877. See the console output for more details. Possible conflicts:
--conflicts Conflict resolved in build ANSIBLE-ROLES-merge#878. See the console output for more details.
Using this latest version (0eaeba6) in https://github.com/ome/omero-server-docker/pull/37
Python 3 support, role should be compatible with old Python 2 installs.
Closes https://github.com/ome/ansible-role-omero-server/issues/42