openstack/barbican-tempest-plugin
Code Issues Proposed changes

Merge "Update gate jobs as per the 2025.1 cycle testing runtime"

Browse Source
This commit is contained in:
Zuul 2024-11-30 20:11:40 +00:00 committed by Gerrit Code Review
commit 2cd185133a
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.zuul.yaml
View File

@ -6,6 +6,7 @@
check: check:
jobs: jobs:
- barbican-tempest-plugin-simple-crypto - barbican-tempest-plugin-simple-crypto
- barbican-tempest-plugin-simple-crypto-jammy
- barbican-tempest-plugin-simple-crypto-secure-rbac - barbican-tempest-plugin-simple-crypto-secure-rbac
- barbican-tempest-plugin-simple-crypto-2024-2 - barbican-tempest-plugin-simple-crypto-2024-2
- barbican-tempest-plugin-simple-crypto-2024-1 - barbican-tempest-plugin-simple-crypto-2024-1
@ -16,6 +17,15 @@
gate: gate:
jobs: jobs:
- barbican-tempest-plugin-simple-crypto - barbican-tempest-plugin-simple-crypto
- barbican-tempest-plugin-simple-crypto-jammy
# TODO(gmann): As per the 2025.1 testing runtime, we need to run at least
# one job on jammy. This job can be removed in 2025.2 cycle.
- job:
name: barbican-tempest-plugin-simple-crypto-jammy
description: This is integrated job testing on Ubuntu jammy(22.04)
parent: barbican-tempest-plugin-simple-crypto
nodeset: openstack-single-node-jammy
- job: - job:
name: barbican-tempest-plugin-simple-crypto name: barbican-tempest-plugin-simple-crypto

2
test-requirements.txt
View File

@ -2,7 +2,7 @@
# of appearance. Changing the order has an impact on the overall integration # of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later. # process, which may cause wedges in the gate later.
hacking>=3.2.0,<3.3.0 # Apache-2.0 hacking>=7.0.0,<7.1.0 # Apache-2.0
python-subunit>=1.0.0 # Apache-2.0/BSD python-subunit>=1.0.0 # Apache-2.0/BSD
oslotest>=3.2.0 # Apache-2.0 oslotest>=3.2.0 # Apache-2.0