Trove's tox tests should respect upper-constraints.txt
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: I8417e0fefae9711d0f71b8f97bbb0e4ea5f8ccf2
Closes-Bug: #1563038
(cherry picked from commit aca90168f52169afb36500d6af77723b1a707008)
Reviewed: https:/ /review. openstack. org/302581 /git.openstack. org/cgit/ openstack/ trove/commit/ ?id=3e6cfdb0891 98c465dcd0e1c83 88808c9979bbd8
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4e3e804f7c375b1 519267d35ab14b8 515106ae6d
Author: Amrith Kumar <email address hidden>
Date: Tue Mar 29 12:07:14 2016 -0400
Trove's tox tests should respect upper-constrain ts.txt
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: I8417e0fefae971 1d0f71b8f97bbb0 e4ea5f8ccf2 fb36500d6af7772 3b1a707008)
Closes-Bug: #1563038
(cherry picked from commit aca90168f52169a
commit 18331be59c9f712 532a1b3ec378865 a7d37b8fa9
Author: Amrith Kumar <email address hidden>
Date: Mon Mar 28 16:10:53 2016 -0400
Address change in Route v2.3
Routes v2.3 which just came out included a change (see the LP bug
referenced below) that caused py27 to fail.
At issue is that Routes<2.3 allowed both
In 2.3, you were required to provide both route_name and
route_path. This change adds a route_name to support both Routes < 2.3
and Routes == 2.3.
Change-Id: I8aa0626960fbf4 46102452a56369d 24420422dac 411230f91b8e23e 72845cbf2a)
Related-Bug: 1563028
(cherry picked from commit 6664fb27af2218c
commit f34581a9d71d296 b699e3d4324a35b f457488074
Author: Thierry Carrez <email address hidden>
Date: Fri Mar 18 09:48:48 2016 +0100
Update .gitreview for stable/mitaka
Change-Id: I5b43aab59d6cdb b9b24a7b5694c1f 9f55fc7c259