On 9 June 2015 at 03:58, Jeremy Stanley <[email protected]> wrote: > On 2015-06-08 13:29:50 +1200 (+1200), Robert Collins wrote: > [...] >> However, we are going to move from test-requirements.txt to setup.cfg >> eventually, but thats a separate transition - and one could still use >> test-requirements.txt there to provide git references. > > Except please don't. If you put a git requirement entry in that file > for neutron, every CI job which uses that test-requirements.txt will > reclone all of neutron over the network from scratch because pip > isn't smart enough to do otherwise unless you take additional > measures to preinstall that requirement in the environment where the > test is run. That's why we use tools like devstack-gate or > zuul-cloner which know how to check for cached repos and update them to > the ref that you've (or that zuul has) requested.
I already said that the git entry should be to a local zuul-cloner cloned repo. Kevin's *current* 3rd-party CI solution is doing full-clones each time. BTW pip can trivially re-use git repositories if you specify the --source path in e.g. pip.conf, but thats a separate discussion IMO :). -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
