Skip to content
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

ansible-core devel dropping controller support for Python 3.9 #49

Closed
21 of 22 tasks
Tracked by #476
s-hertel opened this issue Jun 22, 2023 · 1 comment
Closed
21 of 22 tasks
Tracked by #476

ansible-core devel dropping controller support for Python 3.9 #49

s-hertel opened this issue Jun 22, 2023 · 1 comment

Comments

@s-hertel
Copy link

s-hertel commented Jun 22, 2023

Amending #48:

On July 6th, the version of ansible-core will be updated to drop controller support for Python 3.9. The devel version of the controller will then require Python 3.10, 3.11, or 3.12. Target Python versions are not affected. To develop and test against multiple versions of ansible-core in the same environment, the oldest version used will determine the Python version required.

Oldest ansible-core version used for dev/test Use Python version
2.16 / devel 3.10 - 3.12
2.14 and 2.15 3.10 - 3.11
2.12 and 2.13 3.10

If you maintain a collection tested on Azure Pipelines in the Ansible org:

  • Update .azure-pipelines/azure-pipelines.yml to use quay.io/ansible/azure-pipelines-test-container:4.0.1
  • Remove tests for ansible-core versions 2.11 and earlier

If you maintain a collection tested by another CI system:

  • Ensure your CI system uses a new enough Python version (see the table above)
  • Remove tests for ansible-core versions 2.11 and earlier

The following is a checklist of collections tested on Azure Pipelines which need to update their container version. Many of these will also need to drop end-of-life versions of ansible-core from their test matrix.

  • community.libvirt:main
  • community.postgresql:stable-2
  • community.postgresql:main
  • community.postgresql:stable-1
  • microsoft.ad:main
  • community.rabbitmq:main
  • community.network:main
  • community.network:stable-4
  • community.network:stable-5
  • ansible.windows:main
  • consoledot.edgemanagement:main
  • community.docker:stable-2
  • community.docker:main
  • ansible.posix:main
  • community.windows:main
  • community.crypto:main
  • community.crypto:stable-1
  • community.general:stable-7
  • community.general:stable-6
  • community.general:main
  • community.general:stable-5
  • hetzner.hcloud:main
@ansible-collections ansible-collections locked as resolved and limited conversation to collaborators Jun 23, 2023
@felixfontein
Copy link
Contributor

If you still need to run tests with ansible-core 2.11 or earlier, you need to run them with GHA.

For example community.general still supports Ansible 2.9+, and runs tests with EOL'ed Ansible/ansible-base/ansible-core versions with GHA, and others with AZP. The config files are as follows: https://github.com/ansible-collections/community.crypto/blob/main/.github/workflows/ansible-test.yml and https://github.com/ansible-collections/community.crypto/blob/main/.azure-pipelines/azure-pipelines.yml

@mattclay mattclay closed this as completed Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants