zaqar/.zuul.yaml
98k 67bb865d5c import zuul job settings from project-config
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Ia7cc0ba4bf428458846e7a1fcf5bc2617ca3aa50
Story: #2002586
Task: #24346
2018-09-14 09:55:02 +00:00

29 lines
1.1 KiB
YAML

- project:
templates:
- openstack-python35-jobs
- openstack-python-jobs
- periodic-stable-jobs
- check-requirements
- publish-openstack-sphinx-docs
- release-notes-jobs
name: openstack/zaqar
check:
jobs:
# TripleO jobs that deploy Zaqar.
# 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-scenario002-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.
- tripleo-ci-centos-7-scenario002-multinode-oooq
- tripleo-ci-centos-7-scenario002-multinode-oooq-container
- legacy-rally-dsvm-zaqar-zaqar:
voting: false
gate:
queue: zaqar
jobs:
- tripleo-ci-centos-7-scenario002-multinode-oooq
- tripleo-ci-centos-7-scenario002-multinode-oooq-container