[openstack-dev] [release][infra][zuul][zuulv3][horizon][neutron] project-specific release job templates

Armando M. armamig at gmail.com
Tue Oct 24 23:24:39 UTC 2017

On 24 October 2017 at 13:13, Jeremy Stanley <fungi at yuggoth.org> wrote:

> On 2017-10-24 11:31:56 -0700 (-0700), Armando M. wrote:
> [...]
> > the work on neutron-lib is slowly progressing but it's not close enough
> to
> > allow us to break the dependency that requires neutron sub-projects to
> add
> > neutron to the list of required-projects (which I believe the sort of the
> > error in the release pipeline stems from).
> [...]
> It's not entirely clear to me what about a Neutron plug-in would
> actually require the neutron source installed just to be able to
> generate a tarball (or wheel) or build sphinx docs. Couldn't that be
> solved even if things like installation or unit testing still
> continue to need neutron?

Jeremy and I talked about this in [1].

To sum it up: the necessity of neutron for plugins is primarily for testing
and installation to the best of my knowledge. Other coupling tied to bash
scripts that control gate jobs could be easily addressed if it gets in the
way. Therefore, should we move away from tox for release specific tasks,
it's entirely possible to drop the custom project definition.

I hope I represented the conversation correctly!


> --
> Jeremy Stanley
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171024/d87567c3/attachment.html>

More information about the OpenStack-dev mailing list