From 1acaf917e16564c195238c873ae57abd2a8133e5 Mon Sep 17 00:00:00 2001 From: Mohammed Naser Date: Sat, 16 Jun 2018 16:49:24 -0400 Subject: [PATCH] Use Tempest master when testing roles in master If we're testing a stable branch, it is best to use the stable released Tempest version. However, when working in master, it is possible that an OpenStack service change which has a corresponding Tempest change would lead to things failing because we're deploying master of the service but a tagged version of Tempest which means the tests will fail. In order to ensure stability of stable branches, we'll keep using the tagged release but we'll use master Tempest for testing the roles. Change-Id: I347afd358850149b359ae64871a858701755d896 --- test-vars.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/test-vars.yml b/test-vars.yml index 3edecd95..47f37b30 100644 --- a/test-vars.yml +++ b/test-vars.yml @@ -515,9 +515,10 @@ horizon_secret_key: "SuperSecreteHorizonKey" horizon_external_ssl: False # Tempest specific settings -# We prefer to use the released versions of tempest -# for general role testing as it's more stable. -tempest_developer_mode: False +tempest_git_repo: https://git.openstack.org/openstack/tempest +# We prefer to use the released versions of tempest for stable branches, but +# we deploy the latest for the master branch. +tempest_developer_mode: "{{ test_branch == 'master' }}" tempest_venv_download: False # tempest_venv_bin is set to use the same naming convention # as the other venvs (with the tag 'testing')