On Wed, Mar 30, 2016 at 08:33:06AM -0400, Davanum Srinivas wrote: > Folks, > > Quick primer/refresh because of some gate/CI issues we saw last few > days with Routes===2.3 > > upper-constraints.txt is the current set of all the global libraries > that should be used by all the CI jobs. > > This file is in the openstack/requirements repo: > http://git.openstack.org/cgit/openstack/requirements/tree/upper-constraints.txt > http://git.openstack.org/cgit/openstack/requirements/tree/upper-constraints.txt?h=stable/mitaka > > Anyone working on a project, please ensure that all CI jobs respect > constraints, example from trove below. If jobs don't respect > constraints then they are more likely to break: > https://review.openstack.org/#/c/298850/
While I agree that projects should do this, do keep in mind that projects that do not run tests on openstack/requirements changes still have plenty of room for breaks when u-c changes are merged. :) // jim > > Anyone deploying openstack, please consult this file as it's the one > *sane* set of libraries that we test with. > > Yes, global-requirements.txt has the ranges that end up in project > requirements files. However, upper-constraints.txt is what we test for > sure in OpenStack CI. > > Thanks, > Dims > > -- > Davanum Srinivas :: https://twitter.com/dims > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
