-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
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
Test multiple supported Ansible versions #729
Comments
@schurzi As a hint, we currently address this internally with a combination of poetry, tox and https://github.com/enpaul/tox-poetry-installer. /cc @nejch |
Since poetry is not used here, even plain tox could do this and install different versions based on the tox environment. Recently, hatch has also become more popular for python projects and supports tox-like environments (https://hatch.pypa.io/latest/environment/#dependencies). |
Description
Currently we use the most recent Ansible version to run our tests. But our collection supports also older Ansible releases. To make sure we stay compatible, we need to add tests for the older Ansible versions. Since we already have a lot of tests, we should keep this to a minimum.
Solution
We have no clear solution to this.
Alternatives
Running our Playbooks without executing them against a specific host should cover a lot of possible issues. So using
ansible-lint
or something similar pinned to a specific Ansible version in a matrix build could be a good way to do this.Additional information
No response
The text was updated successfully, but these errors were encountered: