[
https://issues.jenkins-ci.org/browse/JENKINS-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slide-O-Mix closed JENKINS-3670.
--------------------------------
Resolution: Won't Fix
I think this would be too klunky to define in the global config area. I
recommend using the Jelly or Groovy scripting instead and checking the build
status in there and changing the output accordingly.
> Configure 'DefaultContents' per build status
> --------------------------------------------
>
> Key: JENKINS-3670
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3670
> Project: Jenkins
> Issue Type: Improvement
> Components: email-ext
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: jhm
> Assignee: markltbaker
>
> You could configure the $DEFAULT_CONTENT in the Hudson configuration.
> But seeing always the same structure is not required - if the build status is
> success or fixed I dont need the $FAILED_TESTS, $CHANGES or $BUILD_LOG.
> It would be good to configure multiple 'defaults' so each trigger could use
> different defaults. Better than configure them for each job.
> $DEFAULT_CONTENT
> $DEFAULT_CONTENT_SUCCESS
> $DEFAULT_CONTENT_FAILURE
> $DEFAULT_CONTENT_FIXED
> $DEFAULT_CONTENT_UNSTABLE
> $DEFAULT_CONTENT_STILL_FAILING
> $DEFAULT_CONTENT_STILL_UNSTABLE
--
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
