859924eeb4
* Move zuul configuration to .zuul.d directory. It allows to place job definitions into separate files (we have a lot of jobs). * Copy `extra` files to the right folder * Add check for rally results directory existance before fetching it * Stop play if `rally task start` fails with unexpected error code * Export RALLY_PLUGINS_DIR and RALLY_EXTRA_DIR environment variables before launching rally task, to provide backward compatibility. (see https://github.com/openstack/mistral/blob/master/rally-jobs/task-mistral.yaml#L1 ) * Save one line message about happened error * Load custom plugins Change-Id: I1004afb29b9c173e414c59ef54bf58458b5d9422
34 lines
1.0 KiB
ReStructuredText
34 lines
1.0 KiB
ReStructuredText
=====================
|
|
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
|
|
<https://docs.openstack.org/infra/system-config/zuulv3.html>`_ for more
|
|
details.
|
|
|
|
What do we have in this 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.
|