Run sdk functional tests on nova changes
The SDK API tests provide another set of verification of nova behavior. In a perfect world, as we add new microversions to nova, we'd add support for the microversion first to SDK along with a test that should work if the MV isn't there, and then adding the microversion the test should still work - which would allow us to make sure SDK is always up to date with the very latest and greatest nova api. Change-Id: I2406bd6d9e69e33e57b715ff0812c5770b1b53d8
This commit is contained in:
parent
7d30ad26ae
commit
2092c3e714
@ -401,6 +401,8 @@
|
||||
irrelevant-files: *policies-irrelevant-files
|
||||
- tempest-ipv6-only:
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
- openstacksdk-functional-devstack:
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
gate:
|
||||
jobs:
|
||||
- nova-grenade-multinode
|
||||
@ -414,6 +416,8 @@
|
||||
irrelevant-files: *policies-irrelevant-files
|
||||
- tempest-ipv6-only:
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
- openstacksdk-functional-devstack:
|
||||
irrelevant-files: *dsvm-irrelevant-files
|
||||
experimental:
|
||||
jobs:
|
||||
- ironic-tempest-bfv:
|
||||
|
Loading…
Reference in New Issue
Block a user