[all][qa] grenade zuulv3 native job available now and its migration plan

Ghanshyam Mann gmann at ghanshyammann.com
Mon May 4 17:44:22 UTC 2020


 ---- On Mon, 04 May 2020 09:36:47 -0500 Dmitry Tantsur <dtantsur at redhat.com> wrote ----
 > Hi,
 > Somewhat related: do the new jobs finally allow choosing which tests are run rather than blindly run all smoke tests available? It has been a huge problem for ironic since the introduction of upgrade testing, and we're discussing migrating away from grenade because of that.

It does for upgrade tests in the same way you do for devstack job. You can use the tox_envlist and tempest_test_regex.

But the pre-upgrade tests, tests are not configurable.  We discussed those but then left those as it is because of they
are just to verify the installation and not really needed to run by project-specific job.

I think we can disable pre-upgrade tests by default and let projects enabled on a need basis via BASE_RUN_SMOKE.

Will that help?

-gmann

 > Dmitry
 > 
 > On Sat, May 2, 2020 at 2:41 AM Ghanshyam Mann <gmann at ghanshyammann.com> wrote:
 > Hello Everyone,
 > 
 > Finally, after so many cycles, grenade base job has been migrated to zuulv3 native[1]. This is
 > merged in the Ussuri branch.
 > 
 > Thanks to tosky for keep working on this and finish it!!
 > 
 > New jobs 'grenade', 'grenade-multinode', 'grenade-postgresql' and 'grenade-forward' are
 > zuulv3 native now and we kept old job name  'grenade-py3' as an alias to 'grenade' so that it would
 > not break the gate using 'grenade-py3'.
 > 
 > * Start using this new base job for your projects specific grenade jobs.
 > 
 > * Migration to new job name:
 > The integrated template and projects are using old job name 'grenade-py3' need to move to
 > a new job name. Job is defined in the integrated template and also in the project's zuul.yaml for irrelevant-files.
 > So we need to switch both places at the same time otherwise you will be seeing the two jobs running on your gate
 > (master as well as on Ussuri). 
 > 
 > Integrated service specific template has switched to new job[2] which means you might see two jobs running
 > 'grenade' & 'grenade-py3' running on your gate until you change .zuul.yaml. Example: Nova did for master as well as Ussuri gate - https://review.opendev.org/#/q/I212692905a1d645cd911c2a161c13c794c0e0f4d
 > 
 > It needs to be done in Ussuri also as Tempest where integrated templates are present is branchless and apply the change for Ussuri job also.
 > 
 > [1] https://review.opendev.org/#/c/548936/
 > [2] https://review.opendev.org/#/c/722551/
 > 
 > -gmann
 > 
 > 



More information about the openstack-discuss mailing list