Use the dynamic aio scenario
Rather than have to define a job per non-aio service, we have zuul introspect the origin test repo and add the service name to the scenario variable on the fly. This allows us to simplify our job definitions and simply use the AIO job template for all repositories. Change-Id: I86017a181f2d871ded78fc18ef77b01c71323455
This commit is contained in:
parent
7b1ef1e3b3
commit
1d10d5a6fb
|
@ -17,6 +17,7 @@
|
|||
templates:
|
||||
- check-requirements
|
||||
- openstack-ansible-linters
|
||||
- openstack-ansible-deploy-aio_telemetry_metal-jobs
|
||||
- openstack-ansible-deploy-aio_metal-jobs
|
||||
- openstack-ansible-deploy-aio_distro_metal-jobs
|
||||
- publish-openstack-docs-pti
|
||||
- release-notes-jobs-python3
|
||||
|
|
Loading…
Reference in New Issue