[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Markus Hjerto commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Thank you very much, Chris. Your script works perfectly! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Markus Hjerto commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object terryl westerhold, I'm trying to achieve the same goal (JENKINS-16861) but I'm struggling with the script. Do you have something you could share? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Chris Nogradi
commented on JENKINS-12421
Add pre-send step to email-ext that can modify the mail message object
Looks like you mostly had it in the comments for Jenkins-16861. Here is what we use:
build.actions.each { action -
if(action.class.name == "hudson.plugins.claim.ClaimBuildAction" action.isClaimed()) {
logger.println(action.getClaimedBy());
hudson.model.User user = hudson.model.User.get(action.getClaimedBy());
address = user.getProperty(hudson.tasks.Mailer.UserProperty).getAddress() ;
logger.println("Sending to " + address );
msg.setRecipients(javax.mail.Message.RecipientType.TO, address );
}
}
Note that we use the LDAP plugin to talk to ActiveDirectory.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Chris Nogradi commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Oh and I suppose I should mention that we occasionally receive emails from Jenkins with the an email title specifying a project which is different from the body of the email so I think there is a bug in this code that is either caused by not locking a shared resource or a cache value is not flushed properly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Alex Earl commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Are you on the latest version of email-ext? I made some mods that should resolve this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Alex Earl commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object There is already a jira filed by Xavier Nodet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163010#comment-163010 ] SCM/JIRA link daemon commented on JENKINS-12421: Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.jelly src/main/webapp/help/projectConfig/presendScript.html src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/5fa24b49277c865e63148b40d109d3df7c1a5db0 Log: Fix JENKINS-12421 Implement pre-send script that allows modifying or cancelling the sending of the email. Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix resolved JENKINS-12421. --- Resolution: Fixed Implemented an area in the project config for specifying a pre-send script which can modify the email message and even cancel sending the email if desired. Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162884#comment-162884 ] terryl westerhold commented on JENKINS-12421: - Yes, that is what I was thinking. I am curious to know how you are thinking you will approach this issue though. Having a feature that specifically addressed the claim issue would be great, but I really think the more elaborate solution I mentioned in my initial post would be much more beneficial. Giving the option to run a pre-send script after the message was fully built would give me the ability to fix this issue, and the potential to do many other things with the MimeMessage before it was sent. Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162885#comment-162885 ] Slide-O-Mix commented on JENKINS-12421: --- I am planning on adding the groovy feature, I was just wondering where you might want to configure it. If only at the project level (not at the global level and not at the trigger level) it makes it a bit easier :-) Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162869#comment-162869 ] Slide-O-Mix commented on JENKINS-12421: --- Would you want this only at the project level? Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Slide-O-Mix updated JENKINS-12421: -- Summary: Add pre-send step to email-ext that can modify the mail message object (was: 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 -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
[ https://issues.jenkins-ci.org/browse/JENKINS-12421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12421 started by Slide-O-Mix. Add pre-send step to email-ext that can modify the mail message object -- Key: JENKINS-12421 URL: https://issues.jenkins-ci.org/browse/JENKINS-12421 Project: Jenkins Issue Type: New Feature Components: claim, email-ext Affects Versions: current Environment: All Reporter: terryl westerhold Assignee: Slide-O-Mix Labels: claim, email-ext, feature, groovy, jenkins, plugin, script 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
