Update comments about python versions used in sanity checks
... to explain why we need these more clearly and precisely. Change-Id: I9acffef0d85ccb0dfc2c5ebaba7f1c9c72c8435e
This commit is contained in:
parent
9a20147383
commit
04ac053bfd
|
@ -5,7 +5,11 @@
|
|||
parent: tox
|
||||
vars:
|
||||
tox_envlist: sanity # dynamic tox env added by tox-ansible
|
||||
# we want to run sanity only on py3.10 instead of implicit 2.6-3.9 range
|
||||
# We need to use the proper python version depends on the Ansible
|
||||
# version (For example python 3.10 requires Ansible >=2.13). As we pin
|
||||
# Ansible version for sanity environemnt in tox.ini, we pin python
|
||||
# version here. Python 3.10 is now the default Python version in Jammy
|
||||
# and we need to revisit this when we migrate this job to a new version.
|
||||
tox_extra_args: -- --python 3.10
|
||||
|
||||
- job:
|
||||
|
@ -14,8 +18,8 @@
|
|||
parent: tox
|
||||
vars:
|
||||
tox_envlist: units # dynamic tox env added by tox-ansible
|
||||
# we want to run sanity only on py36 instead of implicit 2.6-3.9 range
|
||||
# tox_extra_args: -- --python 3.6
|
||||
# Now we do not pin ansible in the unit environment so we do not pin
|
||||
# Python version explicitly here.
|
||||
|
||||
- job:
|
||||
name: zuul-ansible-role-collect-logs
|
||||
|
|
Loading…
Reference in New Issue