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: Ib25e755b7fcc15b503133060741be77a8ad32f1c
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: Ib913f0fe20af74c9a21875c6a7b497dfa2c30880
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: I9c46c38458e7bddb973ddbb747d2d0b8497e032e
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: I363b193f7619260db8fb3a04e5f7ccb9e46a7f06
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
tempest_plugins -> tempest_services now just the name of the service,
not the plugin package name
Change-Id: I4dd4f82d545cdfb4de48d6d37ee0f28f3e8c6d00
* It overrrides the tripleo-standalone featureset override to run
cinder specific tempest tests.
* It will help to detect the puppet-cinder tempest specific issues early
in gates.
Depends-On: https://review.openstack.org/#/c/610600/
Change-Id: I5c2073db48192f45b36c4555408fb0cdff72c51d
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: I923516fc1c66da513781c6d471c7165403b8bc71
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: I6c8c9468bc7d5a5410a76c7434acbfbd21f1512a
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: I41fb242170d8debe1282d8e9832ede3946ba3352