blob: d95dffc9e9108897b67f835fafd0ec8475598b81 [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
James E. Blair9b0d2772017-08-04 08:48:52 -070013can simply be used by listing ``zuul`` as the trigger.
James E. Blaireff5a9d2017-06-20 00:00:37 -070014
James E. Blair9b0d2772017-08-04 08:48:52 -070015.. attr:: pipeline.trigger.zuul
James E. Blaireff5a9d2017-06-20 00:00:37 -070016
James E. Blair9b0d2772017-08-04 08:48:52 -070017 The Zuul trigger supports the following attributes:
James E. Blaireff5a9d2017-06-20 00:00:37 -070018
James E. Blair9b0d2772017-08-04 08:48:52 -070019 .. attr:: event
20 :required:
James E. Blaireff5a9d2017-06-20 00:00:37 -070021
James E. Blair9b0d2772017-08-04 08:48:52 -070022 The event name. Currently supported events:
23
24 .. value:: project-change-merged
25
26 When Zuul merges a change to a project, it generates this
27 event for every open change in the project.
28
29 .. value:: parent-change-enqueued
30
31 When Zuul enqueues a change into any pipeline, it generates
32 this event for every child of that change.
33
34 .. attr:: pipeline
35
36 Only available for ``parent-change-enqueued`` events. This is
37 the name of the pipeline in which the parent change was
38 enqueued.