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

Andreas Jaeger aj at suse.com
Thu Nov 16 09:59:57 UTC 2017

On 2017-11-15 19:07, Doug Hellmann wrote:
> Excerpts from Akihiro Motoki's message of 2017-11-16 01:32:00 +0900:
>> 2017-11-15 1:06 GMT+09:00 Andreas Jaeger <aj at suse.com>:
>>> On 2017-11-14 17:03, Doug Hellmann wrote:
>>>> Excerpts from Andreas Jaeger's message of 2017-11-14 09:31:48 +0100:
>>>>> On 2017-11-13 22:09, Doug Hellmann wrote:
>>>>>> Excerpts from zuul's message of 2017-11-13 20:37:18 +0000:
>>>>>>> Unable to freeze job graph: Unable to modify final job <Job publish-openstack-releasenotes branches: None source: openstack-infra/project-config/zuul.d/jobs.yaml at master#26> attribute required_projects={'openstack/horizon': <zuul.model.JobProject object at 0x7ff848d06b70>} with variant <Job publish-openstack-releasenotes branches: None source: openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml at master#285>
>>>>>> It looks like there is a configuration issue with
>>>>>> neutron-fwaas-dashboard.
>>>>> Yes, we marked  publish-openstack-releasenotes as final - and then the
>>>>> job added requirements to it.
>>>>> I see at least these two different fixes:
>>>>> - remove the final: true from the job
>>>>> - add neutron and horizon to the job like we done for release job. But
>>>>> there are other projects that have even more requirements.
>>>>> Infra team, what's the best approach here?
>>>>> Andreas
>>>> No projects should even need to install *themselves* much less their
>>>> other dependencies to build release notes. It should be possible to
>>>> build release notes just with sphinx and reno (and their dependencies).
>>> It should - but that's not how those projects seem to be set up ;(
>> The current setup is what most horizon plugins do. It is not special.
>> The release notes of neutron-fwaas-dashboard can be built with sphinx,
>> openstackdocstheme, reno and neutron-fwaas-dashboard itself.
>> I am fine to change this appropriately, but what is the right thing to do?
>> Do we need to change 'releasenotes' env to depend on only sphinx,
>> openstackdocstheme and reno?
>> Akihiro
> 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,


> Doug
> [1] https://governance.openstack.org/tc/reference/project-testing-interface.html#release-notes
> __________________________________________________________________________
> 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

 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