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: I87dbe72efad93f7358add21386c2229008f0e2dc
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: I63e0d9240c35b1075e27aa820c9eaf22792531f4
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Add vars for opensuse-423
Change-Id: I2ba2aab7a7e331763fad4790c5dff1c1006a9b90
There isn't a need to run non-voting jobs in gate, as it ends up just
wasting CI resources. Results can be obtained from the check pipeline
results.
Change-Id: Ic09301ca37d497c3400dd9678cf754c71510410a
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ib527ac4df5a49511e1df85c5c99fe9fd419f5f9b
When 'trove_galera_use_ssl' is True, use an encrypted connection to
the database using either a self-signed or user-provided CA certificate.
A new non-voting test has been added to verify that the role remains
functional when enabling SSL features.
Change-Id: Ia453e842cabbb46e25f9918e88738340ff08f2ab
Partial-Bug: 1667789
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: I636b0900ea2ab001f9363027becd40085653a7f4
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: If0cfb9a2b7b98c492d620bc0fe2324236239d730
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: I6e52632d1549cdff28228866b8fbca993e41a058
