Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8071

Should be able to optionally prevent duplicate email notifications

    Details

    • Similar Issues:

      Description

      There should be a way to configure post-build email notifications such that if the same email address comes up more than once, the recipient won't receive multiple identical emails.

      Example: If 'user@domain.com' is added in the recipient list for a trigger and they are also determined to be one of the committers/culprits, it should be possible to ensure that only 1 email is sent to 'user@domain.com'.

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          The whole point of multiple triggers is to send multiple emails.

          Show
          slide_o_mix Alex Earl added a comment - The whole point of multiple triggers is to send multiple emails.
          Hide
          vitorg Robert Cody added a comment -

          It was already discussed somewhere? I can't find it. But as i see it - the whole point of multiple triggers is to trigger for multiple events and it doesn't refer to e-mails count at all.

          But in most cases triggers produce exactly the same e-mails (however it is just default) and there is no reason to send several same e-mails for the same person. With current UI it's not easy to make e-mails unique across triggers.

          Show
          vitorg Robert Cody added a comment - It was already discussed somewhere? I can't find it. But as i see it - the whole point of multiple triggers is to trigger for multiple events and it doesn't refer to e-mails count at all. But in most cases triggers produce exactly the same e-mails (however it is just default) and there is no reason to send several same e-mails for the same person. With current UI it's not easy to make e-mails unique across triggers.
          Hide
          slide_o_mix Alex Earl added a comment -

          The triggers each allow you to specify a list of people to send to, a different subject, a different body, even different attachment settings, so how is it hard to create a unique email per trigger?

          Show
          slide_o_mix Alex Earl added a comment - The triggers each allow you to specify a list of people to send to, a different subject, a different body, even different attachment settings, so how is it hard to create a unique email per trigger?
          Hide
          vitorg Robert Cody added a comment -

          Yes, that's my point - all trigger e-mails can be customized, so in current UI there is no clear way to resolve the problem. The problem is - there are many triggers and different subscribers, but some subscribers specified in several triggers and all triggers use base template (empty body, subject etc.), so if several triggers run in same time, user will receive several duplicate e-mails. And in current UI there is no way to prevent it.

          The good way to fix this is - if trigger doesn't override any field (so it generates completely same e-mail as another trigger), then there should be only 1 such e-mail for specific subscriber. In more general case - we need to collapse generated e-mails by hash(body/subject/etc.) and then make recipient list unique by passing it in set.

          Show
          vitorg Robert Cody added a comment - Yes, that's my point - all trigger e-mails can be customized, so in current UI there is no clear way to resolve the problem. The problem is - there are many triggers and different subscribers, but some subscribers specified in several triggers and all triggers use base template (empty body, subject etc.), so if several triggers run in same time, user will receive several duplicate e-mails. And in current UI there is no way to prevent it. The good way to fix this is - if trigger doesn't override any field (so it generates completely same e-mail as another trigger), then there should be only 1 such e-mail for specific subscriber. In more general case - we need to collapse generated e-mails by hash(body/subject/etc.) and then make recipient list unique by passing it in set.
          Hide
          slide_o_mix Alex Earl added a comment -

          That might meet YOUR specific need, but the general usage of the plugin would suffer from the change. Each trigger is treated completely separately on purpose.

          Show
          slide_o_mix Alex Earl added a comment - That might meet YOUR specific need, but the general usage of the plugin would suffer from the change. Each trigger is treated completely separately on purpose.

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              csleight csleight
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: