openstack
/
barbican
Code Issues Proposed changes

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
This commit is contained in:
Emilien Macchi 2017-11-18 12:33:38 -08:00
parent a06ca26ae6
commit 5617d605f2
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
.zuul.yaml
View File

@ -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: