• Type: Improvement
• Resolution: Won't Fix
• Priority: Minor
• Component/s: email-ext-plugin
• Labels:

  None

[JENKINS-62074] Send build failure email to approver of pull request

Shivam Lahoti created issue - 2020-04-28 03:31

Shivam Lahoti made changes - 2020-04-28 03:32

Description

Original: The "Send separate e-mails to individuals who broke the build" option sends emails to the commit's committers. However, there are cases when it's better to send emails to the commit's authors instead. We use [Gerrit|https://www.gerritcodereview.com/] for hosting our Git repositories and its workflow consists in pushing commits to pseudo-branches for review. After the commits have been approved they are submitted (integrated) automatically into the real branch, but this action is performed by Gerrit which may have to rebase the original commit in order to be able to tuck it on top of the current branch's HEAD. In these cases, the actual commit's committer becomes an administrative user. In our case we configured it to be a user called *gerrit* with an email like *gerrit@ourdomain.com*. So, for these commits it doesn's work to send notifications to the commit's committer. They should be sent to the commit's author instead. What I propose is that there should exist another configuration option where we could specify a list of emails (a Regexp would also do). If the committer's email matches one of the emails specified, then the notifications should be sent to the commit's author instead. This option should be subordinated to the "Send separate e-mails to individuals who broke the build" option.

Shivam Lahoti made changes - 2020-04-28 03:40

Issue Type

Original: New Feature [ 2 ]

New: Improvement [ 4 ]

Shivam Lahoti made changes - 2020-04-28 03:50

Component/s		New: email-ext-plugin [ 15538 ]
Component/s	Original: mailer-plugin [ 17522 ]

Shivam Lahoti made changes - 2020-04-28 03:55

Description

New: Currently the failure email goes to the developer and Build & Release team members but not to the approver. In case the developer commits the change and then not available after that, the approver does not get to know about the failures unless someone manually contacts him/her.

Ian Williams made changes - 2020-05-02 08:14

Link

New: This issue is duplicated by JENKINS-62079 [ JENKINS-62079 ]

Alex Earl made changes - 2020-08-06 19:32

Resolution		New: Won't Fix [ 2 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]