watcher-tempest-plugin/.zuul.yaml
Ghanshyam Mann 04dd51dcd9 Remove stable/2023.1 job from master gate
stable/2023.1 is planned to be in unmaintained state[1]
and with python 3.8 drop from Tempest[2], we have to pin the
Tempest for stable/2023.1 testing[3]. This means Tempest and
its plugin master does not need to support stable/2023.1.

With that we can remove the stable/2023.1 jobs from tempest
plugin master jobs.

[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/UDQAC7SR5JAQJE5WBAG54A2MTBVBTJ44/
[2] https://review.opendev.org/c/openstack/tempest/+/933398
[3] https://review.opendev.org/c/openstack/devstack/+/933704

Change-Id: I5e75e58c587cbc0055bb66acd9687bd3a97f73de
2024-11-07 17:47:51 +00:00

36 lines
973 B
YAML

- project:
queue: watcher
templates:
- check-requirements
- tempest-plugin-jobs
check:
jobs:
- watcherclient-tempest-functional
- watcher-tempest-functional
- watcher-tempest-actuator
- watcher-tempest-strategies
- watcher-tempest-functional-2024-2
- watcher-tempest-functional-2024-1
- watcher-tempest-functional-2023-2
gate:
jobs:
- watcher-tempest-functional
- job:
name: watcher-tempest-functional-2024-2
parent: watcher-tempest-functional
nodeset: openstack-single-node-jammy
override-checkout: stable/2024.2
- job:
name: watcher-tempest-functional-2024-1
parent: watcher-tempest-functional
nodeset: openstack-single-node-jammy
override-checkout: stable/2024.1
- job:
name: watcher-tempest-functional-2023-2
parent: watcher-tempest-functional
nodeset: openstack-single-node-jammy
override-checkout: stable/2023.2