openstack/project-config
Code Issues Proposed changes

Run requirements update entrypoint from a venv

Browse Source 
The requirements update.py script is growing its own dependencies so
we need to install it into a virtualenv and run it from there. Also,
go ahead and switch to invoking its entrypoint since it'll be
installed for us now. Also run the generate-constraints entrypoint
from a virtualenv similarly.

Change-Id: I16e967356d5c56f1474ee661b954b3db11a608cb
This commit is contained in:
Jeremy Stanley 2015-06-17 01:50:17 +00:00
parent 9d32e99498
commit 607d35d884
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
jenkins/scripts/propose_update.sh
View File

@ -23,8 +23,12 @@ if [ "$OWN_PROJECT" == "requirements" ] ; then
INITIAL_COMMIT_MSG="Updated from global requirements"
TOPIC="openstack/requirements"
PROJECTS=$(cat projects.txt)
VENV=$(mktemp)
trap "rm -rf $VENV" EXIT
virtualenv $VENV
$VENV/bin/pip install -e .
function update {
python update.py $1
$VENV/bin/update-requirements $1
}
elif [ "$OWN_PROJECT" == "openstack-manuals" ] ; then
INITIAL_COMMIT_MSG="Updated from openstack-manuals"
@ -37,10 +41,14 @@ elif [ "$OWN_PROJECT" == "requirements-constraints" ] ; then
INITIAL_COMMIT_MSG="Updated from generate-constraints"
TOPIC="openstack/requirements/constraints"
PROJECTS=openstack/requirements
VENV=$(mktemp)
trap "rm -rf $VENV" EXIT
virtualenv $VENV
$VENV/bin/pip install -e .
function update {
pip install -e .
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3.4 \
$1/global-requirements.txt > $1/upper-constraints.txt
$VENV/bin/generate-constraints -p /usr/bin/python2.7 \
-p /usr/bin/python3.4 $1/global-requirements.txt \
> $1/upper-constraints.txt
}
else
echo "Unknown project $1" >2