This will force pip install to use the upper-constraints.txt specified
version of pip modules. When you don't do this, you are out on the
bleeding edge and become unstable everytime some python library in the
wide world changes in a way that you don't expect.
The releasenotes job has no constraints file, so override the install
command there.
This commit is being proposed on stable/liberty and therefore the
install command includes the clear designation of the branch. This is
because, on branches other than master, we need to be sure to get the
upper-constraints.txt file for that branch.
Reviewed: https:/ /review. openstack. org/338907 /git.openstack. org/cgit/ openstack/ murano- dashboard/ commit/ ?id=beb3a6256e8 3abadf2b8d7a312 6d3dba75394d99
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit beb3a6256e83aba df2b8d7a3126d3d ba75394d99
Author: zhurong <email address hidden>
Date: Wed Jul 6 02:44:05 2016 -0400
Use upper-constraints in tox test environments
This will force pip install to use the upper-constrain ts.txt specified
version of pip modules. When you don't do this, you are out on the
bleeding edge and become unstable everytime some python library in the
wide world changes in a way that you don't expect.
The releasenotes job has no constraints file, so override the install
command there.
This commit is being proposed on stable/liberty and therefore the constraints. txt file for that branch.
install command includes the clear designation of the branch. This is
because, on branches other than master, we need to be sure to get the
upper-
Change-Id: I5eae854d12c604 8d1458ea0d2b1e4 7c4ff910544
Partial-bug: #1598906