Consolidate neutron-tempest-plugin-api with scenario jobs
That way we will run our API tests on the ML2/{OVS,OVN,Linuxbridge}
deployments which will give us slightly better coverage in some cases as
some API extensions may be available only with some specific backends
(see NDPProxy for example, which isn't available on the ML2/OVN case).
This will also allow us to drop neutron-tempest-plugin-api job and
having less jobs with same or better coverage is always good thing :)
Change-Id: Ie34e89636c56783000b4d72a479c23d8d1295002
diff --git a/zuul.d/base-nested-switch.yaml b/zuul.d/base-nested-switch.yaml
index 69e841f..dcc0175 100644
--- a/zuul.d/base-nested-switch.yaml
+++ b/zuul.d/base-nested-switch.yaml
@@ -10,8 +10,8 @@
# Base nested switch job for non EM releases
- job:
- name: neutron-tempest-plugin-scenario-nested-switch
- parent: neutron-tempest-plugin-scenario
+ name: neutron-tempest-plugin-base-nested-switch
+ parent: neutron-tempest-plugin-base
abstract: true
branches: ^(?!stable/(queens|rocky|stein|train|ussuri)).*$
# Comment nodeset and vars to switch back to non nested nodes
@@ -27,6 +27,6 @@
# Base nested switch job for EM releases
- job:
name: neutron-tempest-plugin-scenario-nested-switch
- parent: neutron-tempest-plugin-scenario
+ parent: neutron-tempest-plugin-base
abstract: true
branches: ^(stable/(queens|rocky|stein|train|ussuri)).*$