We have python scripts in the tools/ dir the vast majority of which we
run regularly with python3 via our python3 default basepython in tox.
However, most of these use a `python` shebang line which can be
confusing as to whether or not these scripts run under python3 or not.
To make this more clear set them to python3. I've confirmed the scripts
running under tox are happy with these changes. For the ones that don't
run under tox I've done a quick review and they look happy too.
Change-Id: I983d23c33f7780e5708aa728c829c3262fc99ea0
The OpenDev rename change lost the system-required template for many
repos, add it back.
Update tools/zuul-projects-checks.py to handle this.
Change-Id: I157bdbe5cefb5cbba3fcbb18e24a8bf6e762019c
Check that no entries are added to zuul/projects.yaml that only contain
the project name but do not configure any jobs. These are redundant,
let's remove them.
Change-Id: I048c9011038a38fee4694defc012762079065ce5
We require all projects to have the system-required template ... unless
we aren't gating them which is the case for ansible/ansible and
kata-containers/proxy. That's a bunch of boilerplate though, and zuul
now supports wildcard project configuration.
Make a wildcard config that applies to every project starting with
openstack that contains system-required. Remove the projects that didn't
have anything but that.
Change-Id: Ic1099625ae0500657e01e7cf48bce1273f7e0e24
This is likely to not work yet, but since we aren't gating on
kata-containers/proxy we won't import job config from that repo which
would make these changes self testing. In order to get the ball moving
we need to start somewhere so start here.
This adds a vexxhost specific bionic image which we will start with
until the nodepool azure driver is tested and deployed. We should be
able to make progress on adding jobs and getting the driver going in
parallel this way.
Change-Id: Ia56c2cb3046e31e50014c8bf24342cceacb7db8a
Having the system-required template in place means we're running
merge-check on all ansible patches - and reporting back the results.
We need to stop that.
Change-Id: I75f6086174eb8f64d82185a153a55641425c9632
Experimental jobs are always non-voting, remove the attribute, it's not
needed at all.
Update the linter to handle experimental and periodic-stable pipelines
as well.
Change-Id: Ia00fdbf998402494df2f3e208090484a7cfcfc53
Add a new test that checks for non-voting jobs in pipelines and informs
the user about it.
The report currently is:
Checking voting status of jobs
==============================
Found non-voting job in post:
project: openstack/designate
job: openstack-tox-cover
Found non-voting job in post:
project: openstack/manila
job: openstack-tox-cover
Found non-voting job in post:
project: openstack/murano-dashboard
job: openstack-tox-cover
Found non-voting job in gate:
project: openstack/python-keystoneclient
job: legacy-keystoneclient-dsvm-functional
Found non-voting job in post:
project: openstack/python-muranoclient
job: openstack-tox-cover
Found non-voting job in post:
project: openstack/sahara-tests
job: openstack-tox-cover
(omitting one periodic job)
fix this:
* Remove the non-voting attribute from all post and periodic jobs.
* Remove non-voting job legacy-keystoneclient-dsvm-functional from gate
pipeline.
Change-Id: I41a44902ca2f7bca1e32692efbb29d2884632ef1
The releases repo does extensive checks on the release templates used,
we cannot repeat them here to avoid tight coupling with them.
Add a minimal check that checks that only one of the many release jobs
is used.
Make overall output a bit nicer.
Change-Id: Ifc2ad1e819420b2cb41509b680cbb42e3ebf4d30
Add framework to run checks on zuul.d/projects.yaml.
For now it checks that each project has the system-required template
and that zuul.d/projects.yaml is sorted.
Remove the file tools/zuul-projects_sorted.sh which did a sort test as
well.
Update list of repos so that they are in the order expected (bash and
python string comparison is different).
Change-Id: I29e0b7f49ec890f62d6c521e443248ab33cb819a
Depends-On: I19dbdebc1c02f0ae6ab6671b4cf3fb3c4382a820