Browse code
use master upper-constraints when building tempest venv
The local requirements repo can be checked out to a stable branch,
in which case, the requirements might conflict with tempest's master
requirements.
Master branch's upper-constraints should be used when building tempest's
venv.
Closes-Bug: #1706009
Change-Id: Ifd64638cae2886671421149dbbff3a57f9c64257
Claudiu Belu authored on 2017/06/13 01:32:21Showing 1 changed files
| ... | ... |
@@ -551,7 +551,10 @@ function configure_tempest {
|
| 551 | 551 |
if [[ "$OFFLINE" != "True" ]]; then |
| 552 | 552 |
tox -revenv-tempest --notest |
| 553 | 553 |
fi |
| 554 |
- tox -evenv-tempest -- pip install -c $REQUIREMENTS_DIR/upper-constraints.txt -r requirements.txt |
|
| 554 |
+ |
|
| 555 |
+ # The requirements might be on a different branch, while tempest needs master requirements. |
|
| 556 |
+ git -C $REQUIREMENTS_DIR show master:upper-constraints.txt > u-c-m.txt |
|
| 557 |
+ tox -evenv-tempest -- pip install -c u-c-m.txt -r requirements.txt |
|
| 555 | 558 |
|
| 556 | 559 |
# Auth: |
| 557 | 560 |
iniset $TEMPEST_CONFIG auth tempest_roles "Member" |