Browse code
Default to venv isolated tempest on stable mitaka
Tempest follows global requirements of master on openstack (as it is
branchless) when running tempest in an all in one environment with an
older branch this can cause requirements conflicts. To prevent this
issue we need to venv isolate tempest from the system to ensure that
everything is properly isolated. This also includes no following
constraints since the constraints version on stable is too old for
what we test tempest with.
Change-Id: Ie3d18bf811ae2128737d615f69ea07ad2c535388
Matthew Treinish authored on 2016/05/04 01:31:07Showing 1 changed files
| ... | ... |
@@ -64,7 +64,7 @@ BUILD_TIMEOUT=${BUILD_TIMEOUT:-196}
|
| 64 | 64 |
# This must be False on stable branches, as master tempest |
| 65 | 65 |
# deps do not match stable branch deps. Set this to True to |
| 66 | 66 |
# have tempest installed in DevStack by default. |
| 67 |
-INSTALL_TEMPEST=${INSTALL_TEMPEST:-"True"}
|
|
| 67 |
+INSTALL_TEMPEST=${INSTALL_TEMPEST:-"False"}
|
|
| 68 | 68 |
|
| 69 | 69 |
# This variable is passed directly to pip install inside the common tox venv |
| 70 | 70 |
# that is created |