Clone reqs repo prior to using pip constraints
We pull the pip constraints from the requirements repo so need to clone that repo prior to using the constraints. In fixup_stuff.sh devstack attempts to install packages like prettytable using the constraints. It is also possible to need constraints before fixup_stuff.sh if tracking depends. To deal with this clone requirements repo before any possible use of constraints in pip_install. Change-Id: I42e981c8c5ce1b8a57b9f6cce213065c72d6af11
This commit is contained in:
parent
af68087be3
commit
57aafb5a9a
@ -30,8 +30,6 @@ REQUIREMENTS_DIR=$DEST/requirements
|
||||
# install_infra() - Collect source and prepare
|
||||
function install_infra {
|
||||
local PIP_VIRTUAL_ENV="$REQUIREMENTS_DIR/.venv"
|
||||
# bring down global requirements
|
||||
git_clone $REQUIREMENTS_REPO $REQUIREMENTS_DIR $REQUIREMENTS_BRANCH
|
||||
[ ! -d $PIP_VIRTUAL_ENV ] && virtualenv $PIP_VIRTUAL_ENV
|
||||
# We don't care about testing git pbr in the requirements venv.
|
||||
PIP_VIRTUAL_ENV=$PIP_VIRTUAL_ENV pip_install -U pbr
|
||||
|
5
stack.sh
5
stack.sh
@ -698,6 +698,11 @@ fi
|
||||
|
||||
TRACK_DEPENDS=${TRACK_DEPENDS:-False}
|
||||
|
||||
# Bring down global requirements before any use of pip_install. This is
|
||||
# necessary to ensure that the constraints file is in place before we
|
||||
# attempt to apply any constraints to pip installs.
|
||||
git_clone $REQUIREMENTS_REPO $REQUIREMENTS_DIR $REQUIREMENTS_BRANCH
|
||||
|
||||
# Install Python packages into a virtualenv so that we can track them
|
||||
if [[ $TRACK_DEPENDS = True ]]; then
|
||||
echo_summary "Installing Python packages into a virtualenv $DEST/.venv"
|
||||
|
Loading…
Reference in New Issue
Block a user