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. Depends-On: https://review.opendev.org/658398 Change-Id: Ieee74d4c8195579490936016fe0b4abe3d9b14ae
This commit is contained in:
parent
ae39ab7f2d
commit
8cc12f3fa3
|
@ -17,6 +17,6 @@
|
|||
templates:
|
||||
- check-requirements
|
||||
- openstack-ansible-linters
|
||||
- openstack-ansible-deploy-aio_telemetry_metal-jobs
|
||||
- openstack-ansible-deploy-aio_metal-jobs
|
||||
- publish-openstack-docs-pti
|
||||
- release-notes-jobs-python3
|
||||
|
|
Loading…
Reference in New Issue