d142db453a
+ Add temporary hack for subunit parser that should work before the proper fix is merged to rally project + Temporary turns off coverage job, so we can do not write unittests for fix that should land to rally lib projectg Change-Id: I1149fa83bba28d96bece26c9f978e192cf723de0 |
||
|---|---|---|
| .. | ||
| README.rst | ||
| base.yaml | ||
| docker-jobs.yaml | ||
| rally-task-barbican.yaml | ||
| rally-task-basic-with-existing-users.yaml | ||
| rally-task-cinder.yaml | ||
| rally-task-designate.yaml | ||
| rally-task-heat.yaml | ||
| rally-task-ironic.yaml | ||
| rally-task-keystone-glance-swift.yaml | ||
| rally-task-magnum.yaml | ||
| rally-task-manila.yaml | ||
| rally-task-mistral.yaml | ||
| rally-task-monasca.yaml | ||
| rally-task-murano.yaml | ||
| rally-task-neutron-trunk.yaml | ||
| rally-task-neutron-with-extensions.yaml | ||
| rally-task-neutron.yaml | ||
| rally-task-nova.yaml | ||
| rally-task-octavia.yaml | ||
| rally-task-senlin.yaml | ||
| rally-task-simple-job.yaml | ||
| rally-task-telemetry.yaml | ||
| rally-task-watcher.yaml | ||
| rally-task-zaqar.yaml | ||
| rally-tox-functional.yaml | ||
| rally-verify-tempest.yaml | ||
| zuul.yaml | ||
README.rst
Zuul V3 configuration
Zuul is a pipeline-oriented project gating system. It facilitates running tests and automated tasks in response to Code Review events.
See official doc for more details.
What do we have in this dir?
Note
Do not document all files and jobs here. It will (for sure) become outdated at some point.
- zuul.yaml - the main configuration file. It contains a list of jobs which should be launched at CI for rally-openstack project
- base.yaml - the second by importance file. It contains basic parent jobs.
- All other files are named as like a job for which they include definition.
Where are the actual job playbooks?
Unfortunately, Zuul defines zuul.d (as like .zuul.d) as a directory for project configuration and job definitions.
Ansible roles, tasks cannot be here, so we placed them at tests/ci/playbooks directory.