Now TripleO team is replacing CentOS 8 jobs in master by CentOS 9 jobs.
This follows that and replaces tripleo jobs in puppet repos to switch
to CentOS 9.
Depends-on: https://review.opendev.org/828525
Change-Id: I96aa19a013c79d308e9d87477f9dde010340e932
This change reduces scope of tempest tests in tripleo job, so that we
run only subset of test cases used in TripleO repos.
Change-Id: If1ab96a8b78f47e3316c0a05b27f7827a27ab559
Make standalone job build containers when there is one single
consumer job in layout. Do not run content provider jobs in
this case.
Change-Id: I8f4bb37091fbe3b12ebc86758fd7584505270a7d
https://review.opendev.org/#/c/711320/ adds
tripleo-puppet-ci-centos-8-standalone job in poi and let's
re-use the same parent for tripleo standalone job.
Change-Id: I194ed966bb20005eb21d5a0279eb6a8aa6d1b2d2
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Previously Tripleo validate-tempest role was used to run tempest
on tripleo jobs. Recently we are moving to os_tempest (an unified
role developed by openstack-ansible team).
It moves the vars to os_tempest.
Below is the other var changes:
run_tempest: false -> to disable validate-tempest role
use_os_tempest: true -> enable os_tempest
tempest_whitelist -> tempest_test_whitelist
Change-Id: Ic6ffd3093a7f1b5e40af8c74272aba549f21abac
* It overrrides the tripleo-standalone featureset override to run
glance specific tempest tests.
* It will help to detect the puppet-glance tempest specific issues early
in gates.
Depends-On: https://review.openstack.org/#/c/615178/
Change-Id: Ibcec0829034d968710d7faed9ff733b155bbd2e3
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: I46faa2b65f390bb8febfc372df49842652cc598d
Story: #2002586
Task: #24325
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: I11a8be133a26adc5ce6a30cb017f3cc07d82ed35
Story: #2002586
Task: #24325
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Id98b79930b299259c6e51da01e74f5e7113b1445