Re: [openstack-dev] [neutron] tox-siblings alternative for local testing
On 8/30/18 5:49 AM, Michel Peterson wrote: > > There are pre releases available in PyPI [1]. You can use those from > your requirements like we did in n-odl [2]. > > That might be an acceptable solution. > > [1] https://pypi.org/project/neutron/#history > [2] https://review.openstack.org/#/c/584791/ > IIUC, I don't think consuming pre-releases is really a solution; it's a work-around for this particular case. Any solution should be pulling the appropriate dependencies from source; mimicking what tox-siblings does. This ensures the local testing is done on the latest source regardless of what's on PYPI (a point-in-time snapshot of the code). I believe the same applies to [2] in your email; things aren't going to work as expected locally until you account for pulling from source. We can discuss this more at the PTG, but moving forward I think any projects wanting to get the neutron-lib consumption patches (for free) will need to make sure they have tox/zuul setup properly for both local and gate testing. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] tox-siblings alternative for local testing
On Wed, Aug 29, 2018 at 9:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. > There are pre releases available in PyPI [1]. You can use those from your requirements like we did in n-odl [2]. That might be an acceptable solution. [1] https://pypi.org/project/neutron/#history [2] https://review.openstack.org/#/c/584791/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] tox-siblings alternative for local testing
On 8/29/18 12:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. What we've been doing to date is adding tox target(s) to the respective repo for local testing. These local targets install the dependencies from source where necessary (in place tox siblings). For more details see the "How to setup dependencies for local tox targets" of [1]. This is also a topic I wanted to bring up at the neutron PTG [2]. There maybe other solutions, but I'm unaware of them. [1] https://etherpad.openstack.org/p/neutron-sibling-setup [2] https://etherpad.openstack.org/p/neutron-stein-ptg __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] tox-siblings alternative for local testing
hi, after a recent change [1] , neutron-fwaas' unit tests need an unreleased version of neutron. (the one including the corresponding change [2]) while it's handled by tox-siblings on the gate, it requires extra steps if you want to run the tests locally. is there any preferred solution for this? i guess the simplest solution is to make an intermediate release of neutron and publish it on pypi. i wonder if it's acceptable or not. [1] https://review.openstack.org/#/c/596971/ [2] https://review.openstack.org/#/c/586525/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
