1e4cb1da36
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
33 lines
1.2 KiB
YAML
33 lines
1.2 KiB
YAML
# Changes that run through devstack-tempest-ipv6 are likely to have an impact on
|
|
# the devstack part of the job, so we keep devstack in the main play to
|
|
# avoid zuul retrying on legitimate failures.
|
|
- hosts: all
|
|
roles:
|
|
- orchestrate-devstack
|
|
|
|
# We run tests only on one node, regardless how many nodes are in the system
|
|
- hosts: tempest
|
|
roles:
|
|
- setup-tempest-run-dir
|
|
- setup-tempest-data-dir
|
|
- acl-devstack-files
|
|
# Verify the IPv6-only deployments. This role will perform check for
|
|
# IPv6 only env for example Devstack IPv6 settings and services listen
|
|
# address is IPv6 etc. This is invoked before tests are run so that we can
|
|
# fail early if anything missing the IPv6 settings or deployments.
|
|
- devstack-ipv6-only-deployments-verification
|
|
tasks:
|
|
- name: Run Tempest version <= 26.0.0
|
|
include_role:
|
|
name: run-tempest-26
|
|
when:
|
|
- zuul.branch is defined
|
|
- zuul.branch in ["stable/ocata", "stable/pike", "stable/queens", "stable/rocky", "stable/stein"]
|
|
|
|
- name: Run Tempest
|
|
include_role:
|
|
name: run-tempest
|
|
when:
|
|
- zuul.branch is defined
|
|
- zuul.branch not in ["stable/ocata", "stable/pike", "stable/queens", "stable/rocky", "stable/stein"]
|