rally/zuul.yaml
Boris Pavlovic 234ead2ead Use for samples testing separated job
Samples testing has to go over all files and ensures that all tasks
have proper specs which is time & disk comsuing, it takes up to ~10-15 seconds

However, testing samples is not required in most development cases, only when
new plugins are added, so it makes sense to split it in separate job

Change-Id: I3536226c389fec0f41d84325747dd0f8b6a880f6
2018-03-11 15:48:16 -07:00

58 lines
1.2 KiB
YAML

- job:
name: rally-install-ubuntu-xenial
parent: base
nodeset: ubuntu-xenial
run: tests/ci/playbooks/rally-install/run.yaml
timeout: 1800
- job:
name: rally-install-centos-7
parent: base
nodeset: centos-7
run: tests/ci/playbooks/rally-install/run.yaml
timeout: 1800
- job:
name: rally-database-migration
parent: base
nodeset: ubuntu-xenial
run: tests/ci/playbooks/rally-database-migration/run.yaml
timeout: 1800
- job:
name: rally-tox-self
parent: tox
description: |
Run test for rally project.
Uses tox with the ``self`` environment.
vars:
tox_envlist: self
- job:
name: rally-tox-samples
parent: tox
description: |
Validates rally/samples
vars:
tox_envlist: samples
- project:
check:
jobs:
- rally-database-migration
- rally-install-ubuntu-xenial
- rally-install-centos-7
- openstack-tox-functional
- rally-tox-samples
- rally-tox-self
gate:
jobs:
- rally-database-migration
- rally-install-ubuntu-xenial
- rally-install-centos-7
- openstack-tox-functional
- rally-tox-samples
- rally-tox-self