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

When claimed, stop sending e-mails to individuals who broke the build

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: claim-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      It would be a great feature if it was possible to prevent Jenkins from sending e-mails to individuals who broke the build when the previous failing build already has been claimed.

      One could argue that all effort by everybody should be put into fixing a build when it breaks, but it is not like that here. We have a lot of jobs and if one fails, the show goes on for the other jobs. Only the people listed as recipients in the config and the person who claimed the build needs to get notified. Of course until the build passes again.

      Very useful plugin by the way!

        Attachments

          Issue Links

            Activity

            Hide
            mabahj Markus added a comment -

            There is no interest in this feature? It would certainly reduce the noise in big projects. As of now, no claim information is included in any build failed-emails. As a minimum, it would even help if the emails said "Already claimed build failed in Jenkins" or something.

            Show
            mabahj Markus added a comment - There is no interest in this feature? It would certainly reduce the noise in big projects. As of now, no claim information is included in any build failed-emails. As a minimum, it would even help if the emails said "Already claimed build failed in Jenkins" or something.
            Hide
            aleksas aleksas added a comment -

            This is an issue in my case too. Added a link to an older issue.

            Show
            aleksas aleksas added a comment - This is an issue in my case too. Added a link to an older issue.
            Hide
            mabahj Markus added a comment -

            Could this maybe be implemented via the work done in JENKINS-12421?

            Show
            mabahj Markus added a comment - Could this maybe be implemented via the work done in JENKINS-12421 ?
            Hide
            mabahj Markus added a comment -

            I registered JENKINS-16861 as a email-ext issue, as this new feature also can be implemented there.

            Show
            mabahj Markus added a comment - I registered JENKINS-16861 as a email-ext issue, as this new feature also can be implemented there.
            Hide
            slide_o_mix Alex Earl added a comment -

            With the template support in email-ext, you could easily add the claim information.

            Show
            slide_o_mix Alex Earl added a comment - With the template support in email-ext, you could easily add the claim information.
            Hide
            mabahj Markus added a comment -

            I've found a solution using a pre-send script in the email-ext plugin (JENKINS-12421), so I'll downgrade this to Minor.

            Show
            mabahj Markus added a comment - I've found a solution using a pre-send script in the email-ext plugin ( JENKINS-12421 ), so I'll downgrade this to Minor.
            Hide
            kutzi kutzi added a comment -

            As Alex wrote in JENKINS-21449 this could be solved by implementing a trigger extension point in email-ext

            Show
            kutzi kutzi added a comment - As Alex wrote in JENKINS-21449 this could be solved by implementing a trigger extension point in email-ext

              People

              • Assignee:
                Unassigned
                Reporter:
                mabahj Markus
              • Votes:
                8 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: