Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-08 Thread Robert Collins
On 9 June 2015 at 04:19, Doug Wiegley doug...@parksidesoftware.com wrote: On Jun 8, 2015, at 9:58 AM, Jeremy Stanley fu...@yuggoth.org 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,

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-08 Thread Jeremy Stanley
On 2015-06-09 05:49:35 +1200 (+1200), Robert Collins wrote: 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. Aah, yep, I missed in his reply that it would be a local repo on the filesystem

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-08 Thread Robert Collins
On 9 June 2015 at 03:58, Jeremy Stanley fu...@yuggoth.org 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

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-08 Thread Jeremy Stanley
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

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-08 Thread Doug Wiegley
On Jun 8, 2015, at 9:58 AM, Jeremy Stanley fu...@yuggoth.org 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

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-07 Thread Kevin Benton
It wasn't using zuul at all. It's a super short bash script that just clones the 3rd party repo, checks out the patch, and then runs 'tox -epy27'. I misspoke in my previous email, because it was setup to use test-requirements.txt to pull in neutron. Did I understand your other email that implied

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-07 Thread Robert Collins
On 4 June 2015 at 21:06, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/03/2015 11:08 PM, Robert Collins wrote: ... One question that this raises, and this is why I wrote the email: is there any need to support this at all:- can we say that

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-07 Thread Robert Collins
On 5 June 2015 at 04:54, Kevin Benton blak...@gmail.com wrote: +1. I had setup a CI for a third-party plugin and the easiest thing to do to make sure it was running tests with the latest copy of the corresponding neutron branch was to put the git URL in requirements.txt. We wanted to always

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-07 Thread Robert Collins
On 8 June 2015 at 11:16, Kevin Benton blak...@gmail.com wrote: It wasn't using zuul at all. It's a super short bash script that just clones the 3rd party repo, checks out the patch, and then runs 'tox -epy27'. I misspoke in my previous email, because it was setup to use test-requirements.txt

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-04 Thread Kevin Benton
+1. I had setup a CI for a third-party plugin and the easiest thing to do to make sure it was running tests with the latest copy of the corresponding neutron branch was to put the git URL in requirements.txt. We wanted to always test the latest code so we had early detection of failures. What's

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-04 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/03/2015 11:08 PM, Robert Collins wrote: Hi, right now there is a little used (e.g. its not in any active project these days) previous feature of pbr/global-requirements: we supported things that setuptools does not: to whit, tarball and

[openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-03 Thread Robert Collins
Hi, right now there is a little used (e.g. its not in any active project these days) previous feature of pbr/global-requirements: we supported things that setuptools does not: to whit, tarball and git requirements. Now, these things are supported by pip, so the implementation involved recursing

Re: [openstack-dev] [global-requirements][pbr] tarball and git requirements no longer supported in requirements.txt

2015-06-03 Thread Thomas Goirand
On 06/03/2015 11:08 PM, Robert Collins wrote: Hi, right now there is a little used (e.g. its not in any active project these days) previous feature of pbr/global-requirements: we supported things that setuptools does not: to whit, tarball and git requirements. Now, these things are