Use stable constraint in tox to release Tempest new tag
We are going to release Tempest new tag which work with
the stable/2024.1 constraint so use that in the tox env.
For example: if anyone use Tempest new tag in future say
1 year later then tox env also should use the 2024.1 contstraint for
compatibility instead master.
These need to be move back to master constraint once release is done.
Change-Id: I4e8fe7650f088ecbbbb279c35f8931c71de4ece1
diff --git a/zuul.d/project.yaml b/zuul.d/project.yaml
index c652fe0..68bf5ce 100644
--- a/zuul.d/project.yaml
+++ b/zuul.d/project.yaml
@@ -122,6 +122,7 @@
voting: false
irrelevant-files: *tempest-irrelevant-files
- ironic-tempest-bios-ipmi-direct-tinyipa:
+ voting: false
irrelevant-files: *tempest-irrelevant-files
- openstack-tox-bashate:
irrelevant-files: *tempest-irrelevant-files-2
@@ -155,6 +156,7 @@
- nova-live-migration:
irrelevant-files: *tempest-irrelevant-files
- ironic-tempest-bios-ipmi-direct-tinyipa:
+ voting: false
irrelevant-files: *tempest-irrelevant-files
experimental:
jobs: