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

Add pre-send step to email-ext that can modify the mail message object

    Details

    • Similar Issues:

      Description

      When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to the one who has claimed it. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile.

        Attachments

          Issue Links

            Activity

            terrylwesterhold terryl westerhold created issue -
            terrylwesterhold terryl westerhold made changes -
            Field Original Value New Value
            Description When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to culprits when build is not claimed. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile. When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to culprits when build is not claimed. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile.
            terrylwesterhold terryl westerhold made changes -
            Description When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to culprits when build is not claimed. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile. When the Email-Ext plugin is used in conjunction with the Claim plugin there is no way to configure a project's email options to only send to the one who has claimed it. This results in every person on a team receiving emails for a build they did not break, turning Jenkins emails into something annoying instead of something useful. For someone who knew the code this would be a pretty easy feature to add. And while this would be a good feature, I think a more elaborate solution that would allow Email-ext plugin users to access/modify all parts of the email message (including who the message is being sent to) would be more useful in the long run. Giving users access to all parts of the email message and the option to run a Groovy script after the email has been built, but before the email has been sent would satisfy this feature request and would make the Email-Ext plugin much more versatile.
            slide_o_mix Alex Earl made changes -
            Assignee Slide-O-Mix [ slide_o_mix ]
            slide_o_mix Alex Earl made changes -
            Summary Build failure emails are continually sent to all culprits even if one culprit has already claimed the build Add pre-send step to email-ext that can modify the mail message object
            slide_o_mix Alex Earl made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            slide_o_mix Alex Earl made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            mabahj Markus made changes -
            Link This issue is related to JENKINS-11638 [ JENKINS-11638 ]
            mabahj Markus made changes -
            Link This issue is related to JENKINS-16861 [ JENKINS-16861 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 142787 ] JNJira + In-Review [ 190273 ]

              People

              • Assignee:
                slide_o_mix Alex Earl
                Reporter:
                terrylwesterhold terryl westerhold
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: