tripleo/layout: move order for multinode jobs
Move order for oooq & upgrade jobs so they don't run on newton like it's
the case now.
We don't want to see:
gate-tripleo-ci-centos-7-scenario001-multinode-upgrades-nv
in stable/newton.
@@ -1650,14 +1650,6 @@ jobs:
- ^metadata.json$
- ^spec/.*$
- # tripleo multinode-oooq jobs are only supported from Ocata.
- - name: ^gate-tripleo-ci-centos-7-.*-multinode-oooq.*$
- branch: ^(?!stable/(hammer|liberty|mitaka|newton)).*$
-
- # TripleO Upgrade job has been introduced in Ocata
- - name: ^gate-tripleo-ci-centos-7.*-upgrades.*$
- branch: ^(?!stable/(hammer|liberty|mitaka|newton)).*$
-
# NOTE(emilien): zuul v2 does not allow us to specify files rules for specific projects
# and are global to the jobname.
# It will be done with zuul v3:
@@ -1736,6 +1728,14 @@ jobs:
- ci/environments/scenario005-multinode.yaml
- ci/pingtests/scenario005-multinode.yaml
+ # tripleo multinode-oooq jobs are only supported from Ocata.
+ - name: ^gate-tripleo-ci-centos-7-.*-multinode-oooq.*$
+ branch: ^(?!stable/(hammer|liberty|mitaka|newton)).*$
+
+ # TripleO Upgrade job has been introduced in Ocata
+ - name: ^gate-tripleo-ci-centos-7.*-upgrades.*$
+ branch: ^(?!stable/(hammer|liberty|mitaka|newton)).*$
+
- name: ^gate-tripleo-ci-centos-7-ovb-containers-oooq-nv$
branch: ^(?!stable/(mitaka|newton)).*$
