-
Notifications
You must be signed in to change notification settings - Fork 523
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
Update integration test guide docker flag usage #1731
Conversation
The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system.
Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MatthiasKunnen Thanks for the PR! The changes to the integration test guide look good. I'd appreciate if you could take a look at line 248. Maybe this is the result of the git workflow or something. I'd prefer if that line wasn't touched in this commit as it is separate to the actual update. Cheers.
@@ -72,7 +72,7 @@ outside of those test subdirectories. They will also not reconfigure or bounce | |||
|
|||
.. note:: Running integration tests within containers | |||
|
|||
To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker ubuntu2004``. See the `list of supported container images <https://github.com/ansible/ansible/blob/devel/test/lib/ansible_test/_data/completion/docker.txt>`_ for options (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules). | |||
To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker ubuntu2204``. Get the list of supported container images by running ``ansible-test integration --help`` (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker ubuntu2204``. Get the list of supported container images by running ``ansible-test integration --help`` (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules). | |
To protect your system from any potential changes caused by integration tests, and to ensure a sensible set of dependencies are available we recommend that you always run integration tests with the ``--docker`` option, for example ``--docker ubuntu2204``. Get the list of supported container images by running ``ansible-test integration --help``. Look for *target docker images* (the ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules). |
@oraNod, sorry for this late addition, I would add this part too, what do you think?
This is because the --help
output is quite long and to avoid confusion with the controller docker images section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MatthiasKunnen No problem! That seems helpful to me. I would possibly rephrase it a little though.
Get the list of supported container images by running ``ansible-test integration --help``. You can find available images in the *target docker images* section of the output. The ``default`` image is used for sanity and unit tests, as well as for platform independent integration tests such as those for cloud modules.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've committed a proposal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again @MatthiasKunnen That looks great.
Backport to stable-2.15: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply e2137b1 on top of patchback/backports/stable-2.15/e2137b19a5bbc9cc7406fb5f45af4b3f1a75b421/pr-1731 Backporting merged PR #1731 into devel
🤖 @patchback |
Backport to stable-2.16: 💚 backport PR created✅ Backport PR branch: Backported as #1736 🤖 @patchback |
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1)
Backport to stable-2.17: 💚 backport PR created✅ Backport PR branch: Backported as #1737 🤖 @patchback |
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1)
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1) Co-authored-by: Matthias Kunnen <[email protected]>
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1) Co-authored-by: Matthias Kunnen <[email protected]>
@oraNod, do you want me to follow the steps by patchback for 2.15 #1731 (comment)? |
@MatthiasKunnen Hey, thanks for following up. Sorry for the delay, just got distracted and a bit sidetracked. If you'd like to do that, it would be fine and appreciated. However our general rule is that we always backport from |
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1)
* Update integration test guide docker flag usage The integration guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system. * Point users to the right section in ansible-test integration --help (cherry picked from commit e2137b1)
The integration tests guide linked to a file in the devel branch that gets out-of-sync with the actual supported images on the user's system. Instead, we now instruct the user to run the help flag to get the list of supported images that are actually present on their system.
This relates to, and fixes, ansible-collections/community.general#8683.