Browse Source

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
(cherry picked from commit 49dcf58467)
(cherry picked from commit c40038800c)
(cherry picked from commit 4c71787841)
changes/01/798101/2
Takashi Kajinami 1 year ago
parent
commit
c06f90366d
  1. 20
      .zuul.yaml

20
.zuul.yaml

@ -5,4 +5,22 @@
- puppet-openstack-integration-jobs-all
- puppet-openstack-beaker-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

Loading…
Cancel
Save