ceilometer/.zuul.yaml
ZhongShengping dd42e84a27 Update Python 3 test runtimes for Train
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.

[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html

Change-Id: Ifb40dd40e716c0f07cafce4425e4ac13619d2085
Depends-On: https://review.opendev.org/#/c/641878/
2019-05-09 17:35:02 +08:00

56 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
irrelevant-files: &ceilometer-irrelevant-files
- ^(test-|)requirements.txt$
- ^setup.cfg$
- ^doc/.*$
- ^.*\.rst$
- ^releasenotes/.*$
- ^ceilometer/tests/.*$
required-projects:
- openstack/grenade
- openstack/devstack-gate
- openstack/ceilometer
- project:
templates:
- openstack-cover-jobs
- openstack-python-jobs
- openstack-python3-train-jobs
- publish-openstack-docs-pti
- periodic-stable-jobs
- release-notes-jobs-python3
- openstack-lower-constraints-jobs
check:
jobs:
- grenade-dsvm-ceilometer
- telemetry-dsvm-integration:
irrelevant-files: *ceilometer-irrelevant-files
gate:
queue: telemetry
jobs:
- grenade-dsvm-ceilometer
- telemetry-dsvm-integration:
irrelevant-files: *ceilometer-irrelevant-files
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-standalone
- tripleo-ci-centos-7-scenario002-multinode-oooq
- tripleo-ci-centos-7-scenario002-standalone