We've created integrated linters check job a while back and it's successfully
working for several releases. At the moment we experience difficulties
with future maintenance of the linters check from the openstack-ansible-tests
repo. So instead of fixing current one, we replace it with modern version of
the test.
Change-Id: I73ff28f76aed64cf527cd4c58d25954b5e864f20
Since we copy all release notes to the integrated repo there is not need
in publishing release notes for each repository. We should only verify their
validity and linting.
Change-Id: Icd69125b861d292bfdbfca264e3867e4acf9b469
Infra jobs are more appropriate for testing infra resources, such
as repo server.
Depends-On: https://review.opendev.org/660477
Change-Id: Ie696c1b6b6732d0a59f03351d3135554afc14ce4
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to the
functional testing using the integrated repo. This replaces
the previous role functional test mechanism.
Any additional role tests are left as-is. They will require
some extra implementation in the integrated build before they
can be transferred.
Depends-On: https://review.openstack.org/647840
Depends-On: https://review.openstack.org/648551
Change-Id: I20fb1e774d495e7c25c1ce7575499c54703553ec
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ifaf05f04e68231d21ea40533ebf4c9c97df06c42
Story: #2002586
Task: #24319
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I3d719f47382c27fd66fe64faed75791126157aba
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Depends-On: I2608fc5a0230436cebb0e6c579deae7bd4d7c209
Change-Id: If26a6248be6e941013511bcc6fd4d9a583607832
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I00d4c989f38deb431f82f8dadc4f970c9121c1bc
Initially the intent for adding this was to better test
any patches for roles together before they merge, but it
has had the unintended side-effect of causing patches to
take much longer to merge (because they all get lined up
in a single queue, rather than independent queues) and
a lot more infra resources are used (because a patch
that fails at the top of the queue will result in all
subsequent patches restarting all their tests).
As discussed in the channel, we'd prefer to revert back
to the previous independent queue method of testing. It
has served us well.
Change-Id: I835d15c29b8bea36201b1355dbc7c677ca6d5a67
Currently the linters test is in the project-config
repository, but those are meant to be used for standard
jobs which do not require any repository other than the
one given. Our lint tests use the 'openstack-ansible-tests'
repository, so we should rather use our own job definition.
Change-Id: I97c59b75a17c89f41d22e0ec559fb09b6fcb5e46
Depends-On: I0391ec310c4eede436011a48490e3c524c8ddf4d
This patch implements an initial set of jobs intended to match
the current job execution method. It does not intend to improve
how the jobs are executed - only to replicate what is currently
in openstack-infra/openstack-zuul-jobs and provide the platform
to iterate on.
Change-Id: Ifa650996eb87c6519ea3dfc449ebde92a8d7802d
Jonathan Rosser