[ 
https://issues.jenkins-ci.org/browse/JENKINS-10952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160704#comment-160704
 ] 

Slide-O-Mix commented on JENKINS-10952:
---------------------------------------

Please see if this can be accomplished using the example template on the wiki

https://wiki.jenkins-ci.org/download/attachments/3604514/jenkins-matrix-email-html.template?version=1&modificationDate=1332562186406
                
> Aggregated e-mails for Matrix Projects
> --------------------------------------
>
>                 Key: JENKINS-10952
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-10952
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: email-ext
>    Affects Versions: current
>            Reporter: davec
>            Priority: Minor
>
> The current behavior for matrix projects is to send an individual e-mail for 
> every configuration.  I would like to suggest an option to allow all 
> individual e-mails from each configuration to be aggregated into a single 
> e-mail that contains all of the information that would have been in each 
> individual e-mail.
> The rationale for this is we have a large number of configurations that we 
> perform integration builds on via a Matrix project. Getting bombarded with 20 
> e-mails because of a typo or missing prototype which causes the build to fail 
> on large numbers of configurations is a little bit overkill. Generating a 
> single e-mail with an aggregation of what would have been the individual 
> e-mails is ideal.
> A similar improvement along with a patch was suggested in issue 8590 
> (https://issues.jenkins-ci.org/browse/JENKINS-8590), however it is different 
> from this suggested improvement in the key area of aggregation.  As I 
> commented on issue 8590, that approach does allow a single e-mail to be sent 
> for a failed build, but the e-mail does not contain any of the build log 
> information from each configuration and therefore requires a visit to the 
> jenkins build page to see which configurations actually failed followed by 
> several clicks to dig down to the build logs.  One of the benefits of the 
> individual e-mails is being able to see directly in the e-mails which 
> configurations failed and their respective build logs.  Aggregating this into 
> a single e-mail would provide the best of both.

--
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

        

Reply via email to