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: I1f3746d04f1d339709db2d06d5af1158a39ebd0c
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: I16984f76ef7b8962fa3d242ba0d5b24cca98b4e6
This requires patches to merge at the same time in os_panko,
os_gnocchi and os_aodh which is not possible.
Change-Id: Ic7c98be2464650a89ab2472e34d5f764639b0133
Currently this role doesn't test the integrated jobs.
With the dynamic execution of the roles, this role
also tests the telemetry stack in the metal jobs template.
Depends-On: https://review.opendev.org/659064
Change-Id: I71b829b9b6328a1810b4c084859d1e702f64e2c8
Use the template instead of individual jobs so that we can easily
updat the template as new jobs become available.
The template has the same content as the jobs removed.
Change-Id: Ic83b32df707850ce6fd29a0f12640e401f8a56b0
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.
2. We promote the distro_install jobs, given that they are
all now working.
Change-Id: Ie5d4221f84f30f0476b089cb5144c902b4b07f52
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: Iff61d38ae5400c728c9f358ecbf42c0b04d8f3de
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: I1ad29be5ecff2cdd282778121f859e0d834e04b1
Story: #2002586
Task: #24319
In order to have more centralized configuration, switch the role to use the project-template instead.
Change-Id: I56be24e808cd6128b85326fcb664c934bba3aeae
The extra jobs that we have are not something that is needed, we simply can
set the jobs to non-voting in the project definition and avoid having non
voting jobs.
Change-Id: I072200b1786cc62bf27789f4528c2eeb7f184581
Distributions provide packages for the OpenStack services so we add
support for using these instead of the pip ones.
Change-Id: If6daa1bb784df46e83bbc118981240eb59a1409d
Implements: blueprint openstack-distribution-packages
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I2304baf72d8e7fb25c4e1eb81ed24e06efe56b0b
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: I9a3b95330332af00acffc5ab137798696c1f7313
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
When 'aodh_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: I24f06aeacd92d6eead4100009301e0fb975bc552
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: Ibe58267404e7cbb1be3dff21f2c7eb1ff98ecff5
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: I7a41a6f9b9fe2bbbf62b6b29b3f85e4e50e92417
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: I9bc165a608bba3dedbf6e5d95c577550179b724b
Dmitriy Rabotyagov