Update gate jobs as per the 2025.1 cycle testing runtime
As per 2025.1 testing runtime[1], we need to test on Ubuntu Noble (which will be taken care by depends-on tempest and devstack patches to move base jobs to Noble) and at least single job to run on Ubuntu Jammy (for smooth upgrade from previous releases). This commit adds a new job to run on Jammy which can be removed in future cycle when testing runtime test next version of Ubuntu as default. Depends-On: https://review.opendev.org/c/openstack/tempest/+/932156 [1] https://governance.openstack.org/tc/reference/runtimes/2025.1.html Change-Id: Id7ddf6e39ae8c0de72b2d48d6beed718fcd760ce
This commit is contained in:
Ghanshyam Mann
committed by
Goutham Pacha Ravi
parent
f4b5557058
commit
32da8e27c7
1 changed files with 14 additions and 0 deletions
@@ -164,6 +164,8 @@
name:manila-tempest-plugin-zfsonlinux
description:Test ZFSOnLinux multibackend (DHSS=False) with postgresql db
parent:manila-tempest-plugin-zfsonlinux-base
# https://bugs.launchpad.net/manila/+bug/2087192
nodeset:openstack-single-node-jammy
branches:&ubuntu_jammy_test_image_branches
regex:^stable/(yoga|xena|wallaby|victoria|ussuri)$
negate:true
@@ -250,6 +252,16 @@
MANILA_SETUP_IPV6:false
NEUTRON_CREATE_INITIAL_NETWORKS:true
# TODO(gmann): As per the 2025.1 testing runtime, we need to run at least
# one job on jammy. This job can be removed as per the future testing
# runtime (whenever we start testing Ubuntu 26.04 as default version).
- job:
name:manila-tempest-plugin-lvm-jammy
description:This is integrated job testing on Ubuntu jammy(22.04)
parent:manila-tempest-plugin-lvm
nodeset:openstack-single-node-jammy
- job:
name:manila-tempest-plugin-container
description:|
@@ -863,6 +875,7 @@
check:
jobs:
- manila-tempest-plugin-lvm
- manila-tempest-plugin-lvm-jammy
- manila-tempest-plugin-generic-scenario:
voting:false
- manila-tempest-plugin-generic:
@@ -876,3 +889,4 @@
gate:
jobs:
- manila-tempest-plugin-lvm
- manila-tempest-plugin-lvm-jammy
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.