blob: a23c875a2d80ddb18c6b6c4a53a6228a9488ebb5 [file] [log] [blame]
James E. Blaireff5a9d2017-06-20 00:00:37 -07001:title: Zuul Driver
2
3Zuul
4====
5
6The Zuul driver supports triggers only. It is used for triggering
7pipelines based on internal Zuul events.
8
9Trigger Configuration
10---------------------
11
12Zuul events don't require a special connection or driver. Instead they
13can simply be used by listing **zuul** as the trigger.
14
15**event**
James E. Blair88e53882017-06-23 21:45:07 +010016 The event name. Currently supported:
James E. Blaireff5a9d2017-06-20 00:00:37 -070017
James E. Blair88e53882017-06-23 21:45:07 +010018 *project-change-merged* when Zuul merges a change to a project, it
19 generates this event for every open change in the project.
James E. Blaireff5a9d2017-06-20 00:00:37 -070020
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**
James E. Blair88e53882017-06-23 21:45:07 +010026 Only available for ``parent-change-enqueued`` events. This is the
27 name of the pipeline in which the parent change was enqueued.
James E. Blaireff5a9d2017-06-20 00:00:37 -070028
James E. Blair88e53882017-06-23 21:45:07 +010029**require-approval**
30 This may be used for any event. It requires that a certain kind of
31 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.
James E. Blaireff5a9d2017-06-20 00:00:37 -070036
James E. Blair88e53882017-06-23 21:45:07 +010037**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 a
40 matching approval.