As part of the migration of this project to the independent release
model, we failed to notice that the job template was still tied to a
specific release. We've now introduced a new unversioned job template,
'openstack-python3-jobs' [1], which was can and should use. Do this.
Note that this is effectively a revert of change
Ic93f1c77230d859713ea9bc86065880efa91de7c which attempted to resolve the
same problem in a different way.
[1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286/
Change-Id: Ibf1238bc7c09b4ae9824be81a06f22decfb40873
Depends-On: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286/
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
As os-resource-classes is branchless which means same
master code is run on stable branches too, let's test it
with all the python version supported in those stable branches.
For that, we need to explicitly add the pythn jobs instead of using
the release specific job template. This way, we will explicitly know
that we are testing all supported python versions and do not remove the
older py version testing when the new release template bumps the min python
version like done in Yoga.
In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Change-Id: Ic93f1c77230d859713ea9bc86065880efa91de7c
Adjust tox settings for a reasonable set of job defaults.
Turn on the usual templates in .zuul.yaml
Correct small pep8 and docs issues to get tox jobs passing.
Change-Id: Id0ebeab2ec2439d52defe59096b07c3d0b7bc66d