blob: 18d35a13a2310f699fa056ca3baf3f5bae43782b [file] [log] [blame]
Joshua Hesketh1879cf72013-08-19 14:13:15 +10001:title: Reporters
2
3Reporters
4=========
5
6Zuul can communicate results and progress back to configurable
7protocols. For example, after succeeding in a build a pipeline can be
8configured to post a positive review back to gerrit.
9
10There are three stages when a report can be handled. That is on:
11Start, Success or Failure. Each stage can have multiple reports.
12For example, you can set verified on gerrit and send an email.
13
14Gerrit
15------
16
17Zuul works with standard versions of Gerrit by invoking the
18``gerrit`` command over an SSH connection. It reports back to
19Gerrit using SSH.
20
21The dictionary passed to the gerrit reporter is used for ``gerrit
22review`` arguments, with the boolean value of ``true`` simply
23indicating that the argument should be present without following it
24with a value. For example, ``verified: 1`` becomes ``gerrit review
25--verified 1`` and ``submit: true`` becomes ``gerrit review
26--submit``.
27
28Gerrit Configuration
29~~~~~~~~~~~~~~~~~~~~
30
31The configuration for posting back to gerrit is shared with the gerrit
Joshua Hesketh5fea8672013-08-19 17:32:01 +100032trigger in zuul.conf as described in :ref:`zuulconf`.
33
34SMTP
35----
36
37A simple email reporter is also available.
38
39SMTP Configuration
40~~~~~~~~~~~~~~~~~~
41
42zuul.conf contains the smtp server and default to/from as describe
43in :ref:`zuulconf`.
44
45Each pipeline can overwrite the to or from address by providing
46alternatives as arguments to the reporter. For example, ::
47
48 pipelines:
49 - name: post-merge
50 manager: IndependentPipelineManager
51 trigger:
52 - event: change-merged
53 success:
54 smtp:
55 to: you@example.com
56 failure:
57 smtp:
58 to: you@example.com
59 from: alternative@example.com