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/mitaka 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.
Change-Id: I5eae854d12c6048d1458ea0d2b1e47c4ff910544
Partial-bug: #1598906
(cherry picked from commit dd239e8fd2eabe554c955456892be84b744994b7)
Reviewed: https:/ /review. openstack. org/338114 /git.openstack. org/cgit/ openstack/ murano- dashboard/ commit/ ?id=90ba2a9ee1a 032809a93fcfca2 43f9e195f5c6a3
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 90ba2a9ee1a0328 09a93fcfca243f9 e195f5c6a3
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/mitaka 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 54c955456892be8 4b744994b7)
Partial-bug: #1598906
(cherry picked from commit dd239e8fd2eabe5