tempest/playbooks
Ghanshyam Mann 1e4cb1da36 Use older run-tempest for stable branches
run-tempest is changed recently to add the new variables but
keep supporting the old ones too, for example:
tempest_black_regex, tempest_exclude_regex. and if both
old and new var are used in job definition (parent and child) then
new variables are picked. Because Tempest is branchless, zuul pick
the Tempest master playbooks/roles. That is why job running on stable
branch gate will pick the base job definition from Tempest master.
This way if any stable jobs which were defining the old var and using old
Tempest are broken if any of their parent job define the new var.

This commit pin the older run-tempest role for such stable branches.

Change-Id: If49ab0c31aca5b7837636727096a9bc83f891b1b
2021-07-14 10:38:16 -05:00
..
devstack-tempest-ipv6.yaml Use older run-tempest for stable branches 2021-07-14 10:38:16 -05:00
devstack-tempest.yaml Use older run-tempest for stable branches 2021-07-14 10:38:16 -05:00
post-tempest.yaml Write tempest-multinode-full as zuulv3 native 2018-06-05 12:01:52 +01:00