As 2023.1 is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: Ie4dacf5ecb567f29a93b998b89b97ea874e02fda
stable/wallaby is in EM state. As Tempest and
plugins masters does not support EM stable branches,
QA team is pinning tempest in devstack stable/wallaby
tesitng[1]. With that we do not need to test the
stable/wallaby jobs on master gate
[1] https://review.opendev.org/c/openstack/devstack/+/871782
Change-Id: I79c6c5a676695b22135b21f8b4837f77bd2eb876
As zed is released, we should add its job on master
gate to keep branchless tempest plugins compatible
to stable branch.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html\
Change-Id: If8b9af02d1035bd1fa1e5cf8c307784e8e8d36f2
In 2023.1 cycle. we are moving the default distro
version of Ubuntu to Jammy (22.04)[1] so we need to pin
the nodeset for stable branch job in master gate so that
they continue run on their supporting distro version which is
Ubuntu Focal since stable/victoria.
Also fixing the zuul config error.
[1] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubuntu-jammy.html
Change-Id: I1d4b8d50d6286cf90fd41c5ab95161bad7cd6df3
stable/victoria is in EM state and Tempest is pinned
there so we do not need to test the stable/victoria
jobs on master gate.
Change-Id: I11bfd3026a02bad7cb6336ed66e7d1ef8559d5af
We have stable/yoga released and stable/ussuri is in
'Extended Maintenance' state. Current 'Maintained'
stable branches are yoga, xena, wallaby, and victoria.
As per tempest stable branch testing policy[1], adding the
newly released stable/yoga job and remove the EM stable/ussuri
job.
[1] https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I9c5984e7caabf61c10b9d211a5347799701bf3e1
We have stable/xena released so we should add
their job on master gate to keep branchless tempest
plugins compatible to stable branch.
This also removes the stable/train job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I41705ea681578cfdc510052122abec4838d8c578
We have stable/victoria and stable/wallaby released so we
should add their job on master gate to keep branchless
tempest plugins compatible to those branch.
This also removes the stable/stein job as that is in EM
state now.
Ref: Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
Change-Id: I82edeeac54ad53bcafe8e77ceb8aef382fce5748
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
Most of the Tempest jobs will be migrate automatically once devstack
base job start running on Focal(Depends-On).
Stable jobs testing stable branch needs to keep running on their supported
distro version which is bionic from stein till ussuri.
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-fo$
Change-Id: I72f42951d29a23d01fbe803d553debc76d49acbc
Story: #2007865
Task: #40198
Supported stable branches in maintenance state
(stein, train, ussuri) use the Tempest and plugins master
version for their testing. To make sure master version (new
tests or any changes) is compatible with stable branch testing,
we need to add the stable branches job on the plugins master gate.
Tempest and many other plugins are already testing the stable
branches in same way[1].
Ussuri onwards, Tempest or plugins are py3 only, so we are
running only python3 version of stable jobs
Tempest plugins guide for stable branch testing:
- https://docs.openstack.org/tempest/latest/stable_branch_testing_policy.html
[1] e8f1876aa6/.zuul.yaml (L646)
Change-Id: If109a13873d2ee9ede112952056914dc4c57b4df
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: I2dee7ac8ba73bbf61776fd34c3f9172b425b6873
Story: #2002586
Task: #24313
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Ie4482054a09a8ddbc2108f75cbaea3ee518c9eda
Follow the conventions for naming jobs in Zuul v3: Rename jobs.
For details, see
https://docs.openstack.org/infra/manual/drivers.html#consistent-naming-for-jobs-with-zuul-v3
This change follows the rename in murano repository.
Change-Id: I547d972bb6b82bc93addf19bd3f989e431950ab2
Depends-On: Id3784a6339b444531d118ab39b19f5a316d87872
Needed-By: I042a8724a728aa1c327a6d8e89bd12071f4ab047