| James E. Blair | eff5a9d | 2017-06-20 00:00:37 -0700 | [diff] [blame] | 1 | :title: Zuul Driver |
| 2 | |
| 3 | Zuul |
| 4 | ==== |
| 5 | |
| 6 | The Zuul driver supports triggers only. It is used for triggering |
| 7 | pipelines based on internal Zuul events. |
| 8 | |
| 9 | Trigger Configuration |
| 10 | --------------------- |
| 11 | |
| 12 | Zuul events don't require a special connection or driver. Instead they |
| 13 | can simply be used by listing **zuul** as the trigger. |
| 14 | |
| 15 | **event** |
| 16 | The event name. Currently supported: |
| 17 | |
| 18 | *project-change-merged* when Zuul merges a change to a project, |
| 19 | it generates this event for every open change in the project. |
| 20 | |
| 21 | *parent-change-enqueued* when Zuul enqueues a change into any |
| 22 | pipeline, it generates this event for every child of that |
| 23 | change. |
| 24 | |
| 25 | **pipeline** |
| 26 | Only available for ``parent-change-enqueued`` events. This is the |
| 27 | name of the pipeline in which the parent change was enqueued. |
| 28 | |
| 29 | *require-approval* |
| 30 | This may be used for any event. It requires that a certain kind |
| 31 | of approval be present for the current patchset of the change (the |
| 32 | approval could be added by the event in question). It follows the |
| 33 | same syntax as the :ref:`"approval" pipeline requirement |
| 34 | <pipeline-require-approval>`. For each specified criteria there must |
| 35 | exist a matching approval. |
| 36 | |
| 37 | *reject-approval* |
| 38 | This takes a list of approvals in the same format as |
| 39 | *require-approval* but will fail to enter the pipeline if there is |
| 40 | a matching approval. |