7c1853d67d
This information duplicates what's defined in zuul config files. This was discussed at the last PTG: https://etherpad.opendev.org/p/oct2024-ptg-neutron#L149 Change-Id: I5b125451aed1eaa447f8d1ef4036bcf25a6a8ea4
2.5 KiB
Neutron Jobs Running in Zuul CI
Different kinds of CI jobs are running against patches proposed for Neutron in Gerrit. They have different purposes and complexity. Some jobs are more lightweight (for example, unit tests or linters), while others are more heavyweight (for example, tempest or grenade jobs).
Mainline Tempest and Grenade jobs
Neutron CI runs a number of tempest and grenade (upgrade) jobs in CI. These jobs are required to pass to merge a patch.
Periodic and experimental jobs
Due to a significant number of jobs, not all of them are run on every
patch. Some of them are instead executed periodically or on-demand. The
periodic jobs are run on a schedule, while the experimental jobs are run
on-demand by making a check experimental comment in Gerrit
under a patch.
Where to find job definitions
You may inspect the list of jobs defined for the project by either
looking under zuul.d/ in the Neutron repository or by
visiting the Zuul web interface at https://zuul.opendev.org/
Some jobs are not defined in this repository, but in the neutron-tempest-plugin repository.
Finally, some jobs are defined through templates. Please consult
zuul.d/project.yaml for the list of templates used in the
Neutron project.
Alternatively, you may also inspect the list of jobs in a recent
patch in Gerrit comments. (Note that the list executed for a particular
patch may be affected by irrelevant-files filters. You may
consult these in the zuul.d/ configuration files.)