tempest/zuul.d
Ghanshyam Mann ba28d78c30 Add experimental job to run test with 'latest' microversion
API microversions are inhertied in nature from features points
of view, means higher microversion will have all the features/
changes done in lower microversion.

In Tempest we write the microversion tests by capping
the min and max microversion so that they can request
the API with correct microversion.

But for non microversion tests we do not test if they are
run-able for all the configured microversion in Tempest config
file. To test it at some extend this commit adds a experimental
job to run the API tests (compute and volume) with 'latest'
microversion to know if that run successfully or need modification.

This job is experimental as now as I expect lot of test failure
with the 'latest' microversion and as we keep fixing those and all
the tests pass then we can move it to voting job in check/gate pipeline.

Change-Id: Ie840dd0997519d7e11a661853f9376f43c6e7905
2021-09-03 10:21:54 -05:00
..
base.yaml Decentralize the zuul jobs into zuul.d 2020-11-25 18:03:56 +00:00
integrated-gate.yaml Add experimental job to run test with 'latest' microversion 2021-09-03 10:21:54 -05:00
project.yaml Add experimental job to run test with 'latest' microversion 2021-09-03 10:21:54 -05:00
stable-jobs.yaml Enable swift in tempest-slow-py3 job 2021-06-14 17:09:35 -05:00
tempest-specific.yaml Add stestr master job 2021-04-21 20:19:33 -05:00