Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
On 2017-11-16 11:45, Akihiro Motoki wrote: > 2017-11-16 19:33 GMT+09:00 Andreas Jaeger : >> On 2017-11-16 11:27, Akihiro Motoki wrote: >>> 2017-11-16 18:59 GMT+09:00 Andreas Jaeger : 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, > > Totally agree. > > I think when we migrated to openstckdocstheme version info was shown > in the rendered text > so we started to use version info in conf.py. Some projects started it > and most projects followed it. > After migrating openstckdocstheme there is no visible version info in > the rendered relnotes, > so I think we can drop it. > > Looking at the openstackdocstheme document [1], PDF generation > expects 'release' variable > but AFAIK we only generate HTML version of release notes and I think > we can drop 'release' > and 'version' variables from conf.py. > > [1] https://docs.openstack.org/openstackdocstheme/latest/ Testing now with: https://review.openstack.org/#/c/520373/ Andreas -- 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 __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
On 2017-11-16 11:33, Andreas Jaeger wrote: > On 2017-11-16 11:27, Akihiro Motoki wrote: >> 2017-11-16 18:59 GMT+09:00 Andreas Jaeger : >>> 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 Indeed, it failed, see: http://logs.openstack.org/73/520373/1/check/build-openstack-releasenotes/f3cbb61/ Andreas -- 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 __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
2017-11-16 19:33 GMT+09:00 Andreas Jaeger : > On 2017-11-16 11:27, Akihiro Motoki wrote: >> 2017-11-16 18:59 GMT+09:00 Andreas Jaeger : >>> 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, Totally agree. I think when we migrated to openstckdocstheme version info was shown in the rendered text so we started to use version info in conf.py. Some projects started it and most projects followed it. After migrating openstckdocstheme there is no visible version info in the rendered relnotes, so I think we can drop it. Looking at the openstackdocstheme document [1], PDF generation expects 'release' variable but AFAIK we only generate HTML version of release notes and I think we can drop 'release' and 'version' variables from conf.py. [1] https://docs.openstack.org/openstackdocstheme/latest/ __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
On 2017-11-16 11:27, Akihiro Motoki wrote: > 2017-11-16 18:59 GMT+09:00 Andreas Jaeger : >> 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 -- 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 __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
2017-11-16 18:59 GMT+09:00 Andreas Jaeger : > 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 : 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 +: Unable to freeze job graph: Unable to modify final job >>> publish-openstack-releasenotes branches: None source: openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute required_projects={'openstack/horizon': >>> at 0x7ff848d06b70>} with variant >>> branches: None source: openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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, 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. > > Andreas > >> 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-requ...@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 > > > __ > 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 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
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 : >>> 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 +: >>> Unable to freeze job graph: Unable to modify final job >> publish-openstack-releasenotes branches: None source: >>> openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute >>> required_projects={'openstack/horizon': >> at 0x7ff848d06b70>} with variant >> branches: None source: >>> openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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, Andreas > 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-requ...@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 __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
Excerpts from Akihiro Motoki's message of 2017-11-16 01:32:00 +0900: > 2017-11-15 1:06 GMT+09:00 Andreas Jaeger : > > 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 +: > > Unable to freeze job graph: Unable to modify final job > publish-openstack-releasenotes branches: None source: > > openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > > required_projects={'openstack/horizon': > at 0x7ff848d06b70>} with variant > branches: None source: > > openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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. 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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
2017-11-15 1:06 GMT+09:00 Andreas Jaeger : > 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 +: > Unable to freeze job graph: Unable to modify final job publish-openstack-releasenotes branches: None source: > openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > required_projects={'openstack/horizon': 0x7ff848d06b70>} with variant branches: None source: > openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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 > > Andreas > -- > 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 > > > __ > 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 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
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 +: Unable to freeze job graph: Unable to modify final job >>> publish-openstack-releasenotes branches: None source: openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute required_projects={'openstack/horizon': >>> 0x7ff848d06b70>} with variant >>> branches: None source: openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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 ;( Andreas -- 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 __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
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 +: > >> Unable to freeze job graph: Unable to modify final job >> publish-openstack-releasenotes branches: None source: > >> openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute > >> required_projects={'openstack/horizon': >> 0x7ff848d06b70>} with variant >> branches: None source: > >> openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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). Doug __ 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] [Release-job-failures][neutron][infra] Tag of openstack/neutron-fwaas-dashboard failed
On 2017-11-13 22:09, Doug Hellmann wrote: > Excerpts from zuul's message of 2017-11-13 20:37:18 +: >> Unable to freeze job graph: Unable to modify final job > publish-openstack-releasenotes branches: None source: >> openstack-infra/project-config/zuul.d/jobs.yaml@master#26> attribute >> required_projects={'openstack/horizon': > 0x7ff848d06b70>} with variant > None source: >> openstack-infra/openstack-zuul-jobs/zuul.d/project-templates.yaml@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 -- 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 __ 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