[openstack-dev] [requirements][horizon][neutron] plugins depending on services

Jeremy Stanley fungi at yuggoth.org
Wed Apr 25 14:54:26 UTC 2018


On 2018-04-25 16:40:47 +0200 (+0200), Monty Taylor wrote:
[...]
> * Relax our rules about git repos in test-requirements.txt
> 
> Introduce a whitelist of git repo urls, starting with:
> 
>   * https://git.openstack.org/openstack/neutron
>   * https://git.openstack.org/openstack/horizon
> 
> For the service projects that have plugins that need to test against the
> service they're intending to be used with in a real installation. For those
> plugin projects, actually put the git urls into test-requirements.txt. This
> will make the gate work AND local development work for the scenarios where
> the thing that is actually needed is always testing against tip of a
> corresponding service.
[...]

If this is limited to test-requirements.txt and doesn't spill over
into requirements.txt then it _might_ be okay, though it still seems
like we'd need some sort of transition around release stable
branching to indicate what URLs should be used to correspond to
those branches. We've been doing basically that with release-time
edits to per-repo tox-install.sh scripts already, so maybe the same
workflow can be reused on test-requirements.txt a well?
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180425/97b89638/attachment.sig>


More information about the OpenStack-dev mailing list