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.
Reviewed: https:/ /review. openstack. org/338897 /git.openstack. org/cgit/ openstack/ murano- agent/commit/ ?id=f404fb191a7 d40d2ea5307ea95 e2f8d0786f78df
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit f404fb191a7d40d 2ea5307ea95e2f8 d0786f78df
Author: zhurong <email address hidden>
Date: Wed Jul 6 21:25:45 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: I5c2d878c79dcf1 ce1715218950c07 a39314b16ff
Partial-bug: #1598906