Add Constraints support

Adding constraints support to libraries is slightly more complex than
services as the libraries themselves are listed in upper-constraints.txt
which leads to errors that you can't install a specific version and a
constrained version.

This change adds constraints support by also adding a helper script to
edit the constraints to remove keystonemiddleware.

Change-Id: Ic181afad5bf3dd89a2edfdf9fb3026f85cdc37a6
This commit is contained in:
Tony Breeds 2016-12-21 11:25:36 +11:00 committed by Steve Martinelli
parent 2092d57836
commit abaf1b5bf7
2 changed files with 34 additions and 2 deletions

tools/ Executable file
View File

@ -0,0 +1,30 @@
#!/usr/bin/env bash
# Client constraint file contains this client version pin that is in conflict
# with installing the client from source. We should remove the version pin in
# the constraints file before applying it for from-source installation.
shift 1
set -e
# NOTE(tonyb): Place this in the tox enviroment's log dir so it will get
# published to for easy debugging.
if [[ "$CONSTRAINTS_FILE" != http* ]]; then
# NOTE(tonyb): need to add curl to bindep.txt if the project supports bindep
curl "$CONSTRAINTS_FILE" --insecure --progress-bar --output "$localfile"
pip install -c"$localfile" openstack-requirements
# This is the main purpose of the script: Allow local installation of
# the current repo. It is listed in constraints file and thus any
# install will be constrained and we need to unconstrain it.
edit-constraints "$localfile" -- "$CLIENT_NAME"
pip install -c"$localfile" -U "$@"
exit $?

View File

@ -1,12 +1,14 @@
minversion = 1.6
minversion = 2.0
skipsdist = True
envlist = py34,py27,pep8,releasenotes
usedevelop = True
install_command = pip install -U {opts} {packages}
install_command = {toxinidir}/tools/ {env:UPPER_CONSTRAINTS_FILE:} {opts} {packages}
setenv = VIRTUAL_ENV={envdir}