We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this a request for help?:
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Which installer: Ansible
Which product and version (eg: ansible & collection version - 7.24.2): ansible-core 2.16.2 collection version 10.16.3
Which operating system and version(eg: ubuntu & version - 20.4): RHEL
Which product license (Enterprise/Pro): Enterprise
JFrog support reference (if already raised with support team):
What happened: When we run a deploy & update sometimes we have the download, and then the upgrade skips the relevant tasks.
What you expected to happen: Upgrade
How to reproduce it (as minimally and precisely as possible): Change artifactory_version, run playbook.
Anything else we need to know: Better to grep the version from the property file in the app dir.
The text was updated successfully, but these errors were encountered:
closed via #360
Sorry, something went wrong.
No branches or pull requests
Is this a request for help?:
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Which installer:
Ansible
Which product and version (eg: ansible & collection version - 7.24.2):
ansible-core 2.16.2
collection version 10.16.3
Which operating system and version(eg: ubuntu & version - 20.4):
RHEL
Which product license (Enterprise/Pro):
Enterprise
JFrog support reference (if already raised with support team):
What happened:
When we run a deploy & update sometimes we have the download, and then the upgrade skips the relevant tasks.
What you expected to happen:
Upgrade
How to reproduce it (as minimally and precisely as possible):
Change artifactory_version, run playbook.
Anything else we need to know:
Better to grep the version from the property file in the app dir.
The text was updated successfully, but these errors were encountered: