opendev/system-config
Code Issues Proposed changes

Send email on merge-failure instead of commenting

Browse Source 
Co-Authored-By: Andrew Kerr <andrew.kerr@netapp.com>

Change-Id: I7496cb83e33efe7ae2967d4c58d144e6c0c59d16
This commit is contained in:
Lenny Verkhovsky 2015-07-28 15:02:51 +03:00
parent d67bbc5ee3
commit 10399bcfa8
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/third_party.rst
View File

@ -304,14 +304,22 @@ Here’s a snippet from that file that constructs the ``check`` pipeline taken f
gerrit:
verified: 1
failure:
gerrit:
gerrit:
verified: -1
merge-failure:
smtp:
to: third_party_ci@example.com
from: zuul@example.com
subject: Upstream change {change} has a merge failure
This pipeline is configured to trigger on any Gerrit event that represents a new
patch set created. The matching event will invoke the configured Jenkins job(s)
(discussed next). If all the Jenkins jobs are successful, Zuul will add a comment
to Gerrit with a ``verified +1`` vote, and if any one fails, with a ``verified -1``.
In case of merge failure Third Party CI should not comment, but check merger-debug.log
and recheck the patch manually if needed.
Email will be sent to notify the owner about the issue.
The sample includes other possible configurations, or you can configure your own by
following the `Zuul layout documentation <http://docs.openstack.org/infra/zuul/zuul.html#layout-yaml>`_