ceilometer/.zuul.yaml

60 lines
2.0 KiB
YAML

- job:
name: grenade-dsvm-ceilometer
parent: legacy-dsvm-base
run: playbooks/legacy/grenade-dsvm-ceilometer/run.yaml
post-run: playbooks/legacy/grenade-dsvm-ceilometer/post.yaml
timeout: 10800
required-projects:
- openstack-dev/grenade
- openstack-infra/devstack-gate
- openstack/ceilometer
- job:
name: telemetry-tox-py37
parent: openstack-tox
timeout: 2400
irrelevant-files:
- ^.*\.rst$
- ^api-ref/.*$
- ^doc/.*$
- ^releasenotes/.*$
vars:
tox_envlist: py37
bindep_profile: test py37
nodeset: fedora-latest
- project:
check:
jobs:
- telemetry-tox-py37
- grenade-dsvm-ceilometer:
irrelevant-files:
- ^(test-|)requirements.txt$
- ^setup.cfg$
- telemetry-dsvm-integration
gate:
jobs:
- telemetry-tox-py37
- grenade-dsvm-ceilometer:
irrelevant-files:
- ^(test-|)requirements.txt$
- ^setup.cfg$
- telemetry-dsvm-integration
experimental:
jobs:
# TripleO jobs that deploy Telemetry.
# 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-scenario00(1|2)-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.
# NOTE(sileht): These job takes 3 hours and fail most of the times.
# While other jobs take 20-30 minutes
# We can reenable it when they take less times.
- tripleo-ci-centos-7-scenario001-multinode-oooq
- tripleo-ci-centos-7-scenario001-multinode-oooq-container
- tripleo-ci-centos-7-scenario002-multinode-oooq
- tripleo-ci-centos-7-scenario002-multinode-oooq-container