Re: [openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes
On Sun, 05 Aug 2018 06:44:26 +0900 Matt Riedemann wrote > I've reported a nova bug for this: > > https://bugs.launchpad.net/nova/+bug/1785425 > > But I'm not sure what is the best way to fix it now with the zuul v3 > hotness. We had an irrelevant-files entry in project-config for the > tempest-full job but we don't have that for tempest-full-py3, so should > we just rename that in project-config (guessing not)? Or should we do > something in nova's .zuul.yaml like this (guessing yes): > > https://review.openstack.org/#/c/578878/ > > The former is easy and branchless but I'm guessing the latter is what we > should do long-term (and would require backports to stable branches). Yeah, tempest-full-py3 does not have nova specific irreverent-file defined on project-config side. Just for background, same issue was for other job also like tempest-full and grenade job where tempest-full used to run on doc/test only changes also [1] which is fixed after making the 'files' and 'irrelevant-files' overridable in zuul [2]. IMO same solution can be done for tempest-full-py3 too, I pushed the patch for that [3]. For new job, i feel we should always plan to do it in nova's .zuul.yaml and old entry on project-config side can be move to nova side during job migration work. [1] https://bugs.launchpad.net/nova/+bug/1745405 https://bugs.launchpad.net/nova/+bug/1745431 [2] http://lists.openstack.org/pipermail/openstack-dev/2018-June/131304.html [3] https://review.openstack.org/#/c/589039/ -gmann > > -- > > Thanks, > > Matt > > __ > 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] [nova] tempest-full-py3 rename means we now run that job on test-only changes
Excerpts from Matt Riedemann's message of 2018-08-04 16:44:26 -0500: > I've reported a nova bug for this: > > https://bugs.launchpad.net/nova/+bug/1785425 > > But I'm not sure what is the best way to fix it now with the zuul v3 > hotness. We had an irrelevant-files entry in project-config for the > tempest-full job but we don't have that for tempest-full-py3, so should > we just rename that in project-config (guessing not)? Or should we do > something in nova's .zuul.yaml like this (guessing yes): > > https://review.openstack.org/#/c/578878/ > > The former is easy and branchless but I'm guessing the latter is what we > should do long-term (and would require backports to stable branches). > We don't want to rename the job, because we still want to run both jobs for a time. For what it's worth, as soon as Stein opens up I'm going to be working with the rest of the goal champions to propose patches to move the zuul settings for almost all jobs out of project-config and into each project repo, including all of the stable branches. If you add the settings to the config for nova in project-config before we start that, those patches will include the new settings, for the branches where the jobs run. 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
[openstack-dev] [nova] tempest-full-py3 rename means we now run that job on test-only changes
I've reported a nova bug for this: https://bugs.launchpad.net/nova/+bug/1785425 But I'm not sure what is the best way to fix it now with the zuul v3 hotness. We had an irrelevant-files entry in project-config for the tempest-full job but we don't have that for tempest-full-py3, so should we just rename that in project-config (guessing not)? Or should we do something in nova's .zuul.yaml like this (guessing yes): https://review.openstack.org/#/c/578878/ The former is easy and branchless but I'm guessing the latter is what we should do long-term (and would require backports to stable branches). -- Thanks, Matt __ 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
