ansible-role-collect-logs/zuul.d/layout.yaml
Sagi Shnaidman 715b115733 Exclude tripleo jobs from patterns patches
Tripleo jobs are not required to test a pattern and take a lot of
time to merge it, so let's skip them for pattern patches.
Change-Id: Ic16215ac3534c2c59fd04dd1c45cb4e95b135316
2020-08-04 13:10:36 +03:00

44 lines
1.4 KiB
YAML

---
- job:
name: zuul-ansible-role-collect-logs
description: Validate that zuul can use that role.
parent: base
run: test-playbooks/zuul-ansible-role-collect-logs.yaml
voting: false
roles:
- zuul: opendev.org/openstack/ansible-role-collect-logs
name: collect-logs
irrelevant-files:
- ^vars/sova-patterns.yml$
- project:
vars:
fail_logs_collection: true
templates:
- tripleo-undercloud-jobs
check:
jobs: &jobs
- openstack-tox-linters
- openstack-tox-molecule
# Limit the number of jobs executed while still assuring a relevant
# level of coverage. If specific tasks are to be tested we should
# consider implementing functional tests for them, especially as
# running full integration does not effectively validates that the
# outcome was produced (they still rely on manual verification).
- tripleo-ci-centos-8-scenario001-standalone:
irrelevant-files:
- ^vars/sova-patterns.yml$
- tripleo-ci-centos-8-scenario002-standalone:
irrelevant-files:
- ^vars/sova-patterns.yml$
- tripleo-ci-centos-8-containers-multinode:
irrelevant-files:
- ^vars/sova-patterns.yml$
- zuul-ansible-role-collect-logs
gate:
jobs: *jobs
queue: tripleo
post:
jobs:
- publish-openstack-python-branch-tarball