From 10399bcfa80e3fb7502bd8998553d3a1d05dc476 Mon Sep 17 00:00:00 2001 From: Lenny Verkhovsky Date: Tue, 28 Jul 2015 15:02:51 +0300 Subject: [PATCH] Send email on merge-failure instead of commenting Co-Authored-By: Andrew Kerr Change-Id: I7496cb83e33efe7ae2967d4c58d144e6c0c59d16 --- doc/source/third_party.rst | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/source/third_party.rst b/doc/source/third_party.rst index fadbcd8810..95320014a2 100644 --- a/doc/source/third_party.rst +++ b/doc/source/third_party.rst @@ -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 `_