From 49dcf5846765a0ed07e06409ad9a19a851fdc959 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Fri, 14 May 2021 11:49:27 +0900 Subject: [PATCH] TripleO: Do not use an independent content provide job The tripleo-puppet-standalone template introduces a content provider job and a subsequent job to use containers built by the content provider job. This is inefficient because we run only a single tripleo job. Change-Id: Idb5b832d3243fd32b7d48615c7f41f96ce9054b8 --- .zuul.yaml | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/.zuul.yaml b/.zuul.yaml index 04b9f5f7..66327e25 100644 --- a/.zuul.yaml +++ b/.zuul.yaml @@ -5,4 +5,22 @@ - puppet-openstack-integration-jobs-all - puppet-openstack-litmus-jobs - release-notes-jobs-python3 - - tripleo-puppet-standalone + check: + jobs: + - puppet-openstacklib-tripleo-standalone + gate: + jobs: + - puppet-openstacklib-tripleo-standalone + +- job: + name: puppet-openstacklib-tripleo-standalone + parent: tripleo-puppet-ci-centos-8-standalone + description: | + TripleO standalone Job running basic tests + vars: + build_container_images: true + featureset_override: + run_tempest: false + tempest_test_whitelist: + - 'tempest.scenario.test_server_basic_ops' + use_os_tempest: true