This change reduces scope of tempest tests executed in TripleO job
so that we run the same set of Octavia tests as the ones used in
tripleo-ci-centos-N-scenario010-standalone job in TripleO repos which
enables Octavia with Amphora driver.
Change-Id: I3d879b2b8dd6110dfc1949d377c36c9cc3686ed7
This patch redefines the puppet-octavia-tripleo-standalone job based on
tripleo-ci-centos-8-scenario010-standalone, to fix the tripleo
standalone job currently broken.
The difference between puppet-octavia-tripleo-standalone and
tripleo-ci-centos-8-scenario010-standalone is that we use
tripleo-puppet-ci-centos-8-standalone as its base job so that we can
make all tripleo jobs in puppet projects non-voting in a single place.
Change-Id: I4b1ded4d16d84e9324462c405eb9ecddd907ae1b
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: I9b41d69bf7d4c0b5d2c8ce0359fe3551f168ab2f
This patch adds some missing parameters in tripleo job definitions,
which should have been added in the previous change[1].
[1] d311b7f7daa5427217b467e433d4ef050b64f422
Change-Id: If524871ba2f069869e10a92ad42c97b832347d3c
This patch replaces tripleo job definition by the one which is based
on tripleo-puppet-ci-centos-8-standalone, so that we can disable all
tripleo job for puppet modules in a single place.
Change-Id: I3165227e0c92e5e9b38519b6f35633771c8467a0
Job tripleo-ci-centos-8-scenario010-standalone tests a TripleO
deployment with Octavia enabled which heavily relies on puppet-octavia,
providing additional test coverage to the project.
Change-Id: I8b52c1a2ef70463ec0bca7bf1f41f0f00becdc4f
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: I872fcee7b1a52e8453eab5f3868a77d580c97f52
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: Ie45ed0d3eb99d6b4daa69770e3509078c2e722a8
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: I3cc987809ca4aae4e1a1737035f1ef73149877e0