We switch from Fedora 35 to Ubuntu Jammy for this testing because Ubuntu
Jammy is an LTS release that will be supported for 5 years, but Fedora
35's total supported time period is about 13 months some of which is now
gone.
Depends-On: https://review.opendev.org/c/opendev/base-jobs/+/840355
Change-Id: I3025679a4747155a91e88a65dcb4f946a329fba1
siblings: python2.7 ConfigParser has no __getitem__
Constrain soupsieve to <2 for python2.7
Add python2-dev to bindep for subprocess32
Change-Id: If9d6a0ae1a62a94dcec11f6bf637ffee7f0f4fc9
In order to build subprocess32 which comes in as a dependency, you need
gcc or otherwise you'll end up with:
configure: error: in `/tmp/pip-install-bgksUt/subprocess32':
configure: error: no acceptable C compiler found in $PATH
Change-Id: I9b213899f9636fdbc7c054c15ccae4d88b150d40
ansible-lint now supports settings in a file, including exclude_paths.
This lets us simplfy the ansible-lint command. Also, stop installing
zuul and just use a fake zuul_return and zuul_console
to fake out ansible-lint.
Change-Id: I1482a9ab915cec2d45695b60cdbeb93d58cb392c
So that the syntax check which runs on playbooks can find zuul_return.
Add re2 library to bindep, it's needed for zuul.
Change-Id: I93213ee19652c0ec9f4bc699204e9445a1e891c8
The original idea was that we'd have a "python27" job. But it turns out
that "python27" isn't actually as universal as you might think.
"tox-py27" on the other hand is a thing that can and should always work
for people who want to run tox with the py27 env.
Port in the jobs we had in openstack-zuul-jobs.
Also, copy in the text of the old shell scripts so that we can iterate on
them and make them better piecemeal.
These are named zuul-tox not tox because we already have tox jobs
defined elsewhere. We'll need to do the naming dance while we work on
them.
Change-Id: I813f3f2ae138c07918556bc81655518023527131
Dr. Jens Harbott