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: If8e378dcbbd5a74638665c2dcd317e6df0a0833c
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: Iecb6464941097057cad39e50e3626b9abbe84921
Currently this role doesn't test the integrated jobs.
With the dynamic execution of the roles, this role
also get tested by the integrated repo.
Change-Id: I340707627f72fd03de10b0af6ad8f3025a8931de
This patch adds the Debian jobs for this role to make sure
it's always passing as well as updates the meta to reflect
it's support of Debian accordingly.
Depends-On: I9a92b73c419a0dc1cca40dacfef75de61a61db94
Change-Id: I9f1d64c299e3dbe8c3f182f722b9d0a1aa705b80
In order to do a more complete verification of any patches,
we add a full uncontainerised OpenStack deployment to do the
functional testing using the integrated repo. This replaces
the previous 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.
There are some developer mode references that are causing the
role to not run properly due to an undefined variable.
Depends-On: https://review.openstack.org/647840
Depends-On: https://review.openstack.org/648502
Depends-On: https://review.openstack.org/648551
Change-Id: Ia55b9d4e6b2956c226bc287263596a9315964cb1
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: I98f72a38a203a6c36ce1c6243ac12c337fea5314
Story: #2002586
Task: #24319
Now that we're using the general templates, we can slim down
the role test definitions. We can also remove tests which are
not being watched, or which are fundamentally broken. With
this we can also remove unused scripts/plays.
We do the following:
1. We remove the 'ssl' job, given that the person working on
that is no longer doing so, and no-one else has picked up
the work.
Change-Id: I2aac4caa7b1d1eb32212b39a973a76681618c555
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: I9b1c5c1b4a46f1a5424a0a5ffa6cbdf5e9d43fb5
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role
to use the project-template instead.
Depends-On: I3df2c670beeb78baaa1515bcd27e8f2b0d95b3a9
Change-Id: Ic1f54fb2b626f7e194fc89b6df5eb6afc6897c80
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: I3fc0e1597785ee101f362c028744da466a141ded
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: I653e5c9d3921c06a8c09681f235c2cc6fbc69d08
When 'sahara_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: Ie39024c99cad0932f464707adc43019bc1062317
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: I622f33f14782c0fe45d6db33a629014e1e6fb284
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: I2a553d3a236d3a86c776c3120e44968538ace87a
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: I79d4b08e48207b067ff27925ae3f20df3e8d6127
Dmitriy Rabotyagov