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: Id3033cfd18f074c8665d0c9f580ec4076415c599
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: I8d9b29e345501f7a2475b43144d98169c553e1db
Currently this role doesn't test the integrated jobs.
With the dynamic execution of the roles, this role
also tests the blazar role in the metal jobs template.
Change-Id: I457c8e42ded7fd60523b79d8924f4c7dd153a995
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: I3bf65f8188421a7442b0a7b7aec293ec45bbd7ee
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.
Depends-On: https://review.openstack.org/647840
Depends-On: https://review.openstack.org/648502
Depends-On: https://review.openstack.org/648551
Change-Id: Ib62c054823523d5136ff1d3ed68d886ab43de68a
The functional test check the responsiveness of the Blazar API. A
return of 204 code from the API verifies the success.
Rest of the changes ensure compliance with all the standards required
to make the linter and docs tests pass.
Change-Id: I640877817ad1ae312436932af87ad15094616f12
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: I222c0bd402759caef71f5d7525fe15ac7d2ea191
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: Ifa012564ebb347302160bec08b9d2cca4dede57d
Story: #2002586
Task: #24319
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: I45d7316b7c7392ebe6b50b590cac8790cbdf44d3
This introduces the most basic jobs for blazar, and makes
sure blazar passes lint tests.
This reverts commit a5b35ebf11,
effectively re-enabling zuul jobs, and adapts the role
to our latest standards (The lint tests were failing, as
the passwords were logged while setting up Blazar server)
Functional testing starts with -nv only. However, in this
commit we added the necessary `rabbitmq_all` group to
the infra1 group, to help further functional testing.
Co-Authored-By: Taseer Ahmed <taseer94@gmail.com>
Change-Id: Ic2560b53aebf69e4784ce56db6929fe010e6b11e
Dmitriy Rabotyagov