From 5617d605f2e12840933e4a9d6417912cdbb811d5 Mon Sep 17 00:00:00 2001 From: Emilien Macchi Date: Sat, 18 Nov 2017 12:33:38 -0800 Subject: [PATCH] zuul: run tripleo-scenario002 job Like before with legacy jobs, change the zuul v3 layout to run tripleo scenario002 as non voting, that deploys Barbican. Change-Id: I92f7d32218685e38ba2637b9a46f4843d9b5fe6d --- .zuul.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/.zuul.yaml b/.zuul.yaml index cd514b56a..cf5384663 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -163,6 +163,18 @@ - barbican-dogtag-devstack-functional-fedora-26 - barbican-kmip-devstack-functional - grenade-devstack-barbican + # TripleO jobs that deploy Barbican. + # Note we don't use a project-template here, so it's easier + # to disable voting on one specific job if things go wrong. + # tripleo-ci-centos-7-scenario002-multinode-oooq will only + # run on stable/pike while the -container will run in Queens + # and beyond. + # If you need any support to debug these jobs in case of + # failures, please reach us on #tripleo IRC channel. + - tripleo-ci-centos-7-scenario002-multinode-oooq: + voting: false + - tripleo-ci-centos-7-scenario002-multinode-oooq-container: + voting: false gate: queue: barbican jobs: