[openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed

Andreas Jaeger aj at suse.com
Thu Nov 16 10:33:49 UTC 2017

On 2017-11-16 11:27, Akihiro Motoki wrote:
> 2017-11-16 18:59 GMT+09:00 Andreas Jaeger <aj at suse.com>:
>> On 2017-11-15 19:07, Doug Hellmann wrote:
>>> [...]
>>> Someone needs to figure that out. Unfortunately, I don't have the
>>> bandwidth right now. Maybe you, or someone else from one of the affected projects, can work on it?
>>> Two options have been discussed so far:
>>> 1. Create special jobs for neutron and horizon projects that install
>>>    neutron or horizon, like we do for the release jobs.
>>> 2. Redefine the release notes job so that it doesn't use tox
>>>    but installs only the pieces it needs to run a sphinx build. The
>>>    CTI is already defined in a way to support that [1].
>>> My current preference is for option 2. There may be other options
>>> that we haven't explored, though.
>> I gave it a try in https://review.openstack.org/520362. Note that this
>> is only the building part, publishing part is separate - let's first
>> iterate on this one,
> I noticed most projects require to install themselves now to set
> 'version' and 'release' variables in releasenotes/source/conf.py.
> For example, http://git.openstack.org/cgit/openstack/nova/tree/releasenotes/source/conf.py#n51
> I think we cannot build release notes without installing a project itself.

That's really sad ;(

But why would we need to set version and release for the releasenotes at
all? We only have one - unversioned - document.

I suggest to just get rid of it,
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG Nürnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

More information about the OpenStack-dev mailing list