Email-ext plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID email-ext Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
2.37.2.2
Mar 08, 2014
1.532.1
analysis-core (version:1.41, optional)
token-macro (version:1.9)
mailer (version:1.5)
maven-plugin (version:1.409)
config-file-provider (version:2.7.1, optional)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Ash Lux (id: ashlux)
Kyle Sweeney (id: kdsweeney)
K. R. Walker (id: krwalker)
Seiji Sogabe (id: ssogabe)
Alex Earl (id: slide)
Usage Installations 2013-Apr 17078
2013-May 17515
2013-Jun 17938
2013-Jul 18843
2013-Aug 19103
2013-Sep 19767
2013-Oct 20510
2013-Nov 20691
2013-Dec 20724
2014-Jan 21905
2014-Feb 22742
2014-Mar 23824

This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.

Recipes

Additional recipes for email-ext can be found here.

General

This plugin extends Jenkins built in email notification functionality by giving you more control.  It provides customization of 3 areas.

  • Triggers - Select the conditions that should cause an email notification to be sent.
  • Content - Specify the content of each triggered email's subject and body.  
  • Recipients - Specify who should receive an email when it is triggered.

Configuration

Global configuration

Before using email-ext on a project, you must configure some global settings.  Go to Jenkins System configuration page.  Manage Jenkins -> Configure System

The section titled Extended E-mail Notification is where you can configure global email-ext properties.  The properties here should match the settings for your smtp mail server.  This section is set up to mirror Jenkins own email Publisher Reporter (It's different extension point), however there are a few additions.  The inputs labeled Default Subject and Default Content, allow you to configure the email content on a global level.  The input labeled Default Recipients can be used to set a default list of email addresses for all projects using plugin (it can be overridden at the project level). This can be used to greatly simplify the configuration you need to do for all projects.

Project configuration

For a project to use the email-ext plugin, you need to enable it in the project configuration page.  Select the checkbox labeled "Editable Email Notification" in the  "Post-build Actions" section.

Basic Configuration

There are three fields that you can edit when the plugin is enabled.

  • Global Recipient List - This is a comma (or whitespace) separated list of email recipients.  Allows you to specify a single recipient list for each email that is sent.
  • Default Subject - This allows you to configure a token (more about tokens later), that can be used to easily configure all email subjects for the project.
  • Default Content - Same as Default Subject, but for the email body instead of the subject.
Advanced configuration

To see the advanced configuration for the plugin, first click on Override Global setting checkbox, then click the "Advanced" button.  This section allows you to specify recipients for each type of email trigger as well as a pre-send script that can be used to modify the email just prior to sending. 

Pre-send Script

The pre-send script is a feature which allows you to write a script that can modify the MimeMessage object prior to sending. This would allow adding custom headers, modifying the body, etc. Predefined variables include:

  • msg - the MimeMessage object which can be modified
  • logger - a PrintStream and will write to the job's log. 
  • build - the build this message belongs to
  • cancel - a boolean, which when set to true will cancel the sending of the email
Triggers

By default, the only trigger configured is the "Failure" trigger.  To add more triggers, select one from the dropdown, and it will be added to the list.  Once you have added a trigger, you have several options.  If you click "?" (question mark) next to a trigger, it will tell you what conditions must be met for it to send an email.

  • Send to Recipient List - Check this checkbox if you would like to have the email sent to the "Global Recipient List" configured above.
  • Send to Developers  - Check this checkbox to send the email to anyone who checked in code for the last build.  The plugin will generate an email address based on the committer's id and an appended "default email suffix" from Jenkins's global configuration page.  For instance, if a change was committed by someone with an id "first.last", and the default email suffix is "@somewhere.com", then an email will be sent to "first.last@somewhere.com"
  • Send To Requester - If this is checked, an email will be sent user who triggers the build (if triggered by a user manually).
  • Include Culprits - If this is checked AND Send To Developers is checked, emails will include everyone who committed since the last successful build.
  • More Configuration - Configure properties at a per-trigger level.
    • Recipient List - A comma (and whitespace) separated list of email address that should receive this email if it is triggered.  This list is appended to the "Global Recipient List" above.
    • Subject - Specify the subject line of the selected email.
    • Content - Specify the body of the selected email.
  • Remove - Click the delete button next to an email trigger to remove it from the configured triggers list.
Email tokens

The email-ext plugin uses tokens to allow dynamic data to be inserted into an email subject line or body.  A token is a string that starts with a $ (dollar sign) and is terminated by whitespace.  When an email is triggered, any tokens in the subject or content fields will be replaced dynamically by the actual value that it represents.  Also, the "value" of a token can contain other tokens, that will themselves be replaced by actual content.  For instance, the $DEFAULT_SUBJECT token is replaced by the text (and other tokens) that is in the Default Subject field from the global configuration page.  Similarly, the $PROJECT_DEFAULT_SUBJECT token will be replaced by the value of the Default Subject field from the project configuration page

The email-ext plugin sets the email content fields with default values when you enable it for your project.  The Default Subject and Default Content fields on the project config page default to $DEFAULT_SUBJECT and $DEFAULT_CONTENT (respectively), so that it will automatically use the global configuration.  Similarly, the per-trigger content fields default to $PROJECT_DEFAULT_SUBJECT and $PROJECT_DEFAULT_CONTENT, so that they will automatically use the project's configuration.  Since the value of a token can contain other tokens, this provides different points of configuration that can allow you to quickly make changes at the broadest level (all projects), the narrowest level (individual email), and in between (individual project).

To see a list of all available email tokens and what they display, you can click the "?" (question mark) associated with the Content Token Reference at the top bottom of the email-ext section on the project configuration screen.

Token Macro Tokens

As of version 2.22, email-ext supports tokens provided by the token-macro plugin. You can see the available token-macro token below the email-ext tokens when you click the "?" (question mark) associated with the Content Token Reference at the bottom of the email-ext section on the project configuration screen.

Jelly content

New to version 2.9 is the ability to use Jelly scripts. Jelly scripts are powerful in that you can hook into the Jenkins API itself to get any information you want or need. There are two Jelly scripts packaged with the plugin and it is possible to write your own too.

There are two default Jelly scripts available out of the box; one is designed for HTML emails and the other is design for text emails. See the screenshots to the right for what these templates look like. You can specify which script you want by using the template argument. The usage for each script is the following:

  • Text only Jelly script: ${JELLY_SCRIPT,template="text"}
  • HTML Jelly script: ${JELLY_SCRIPT,template="html"}

You can also write your own Jelly scripts. The Jelly scripts are particularly powerful since they provide a hook into the Jenkins API including hudson.model.AbstractBuild and hudson.model.AbstractProject. For example on how to do this, take a look at the existing html and text scripts.

Using custom Jelly scripts (those not packaged with email-ext) requires the cooperation of your Hudson administrator. The steps are relatively simple:

  1. Create the Jelly script. The name of the script should be <name>.jelly. It is important the name ends in .jelly.
  2. Have your Jenkins administrator place the script inside $JENKINS_HOME_\email-templates_.
  3. Use the Jelly token with the template parameter equal to your script filename without the .jelly extension. For example, if the script filename is foobar.jelly, the email content would look like this ${JELLY_SCRIPT,template="foobar"}.

Jelly script tips:

  • You get object of other plugin actions by querying build actions like: ${it.getAction('hudson.plugins.fitnesse.FitnesseResultsAction')}
  • Then you need to know what all functions are allowed by this action object and traverse through result.
Script content

New to version 2.15 is the ability to use Groovy scripts. Scripts are powerful in that you can hook into the Jenkins API itself to get any information you want or need. There are two scripts with corresponding templates packaged with the plugin and it is possible to write your own too.

There are two default scripts and templates available out of the box; one is designed for HTML emails and the other is design for text emails. You can specify which script you want by using the script _argument, you can also just leave the default script and specify a different template file using the _template argument. Further, you can also include an init script that does some initialization using the init argument. The usage for each script is the following:

  • Text only template: ${SCRIPT, template="groovy-text.template"}
  • HTML template: ${SCRIPT, template="groovy-html.template"}

You can also write your own scripts and templates. The scripts are particularly powerful since they provide a hook into the Jenkins API including hudson.model.AbstractBuild and hudson.model.AbstractProject. For example on how to do this, take a look at the existing html and text scripts.

Using custom scripts (those not packaged with email-ext) requires the cooperation of your Jenkins administrator. The steps are relatively simple:

  1. Create the script/template. The name of the script end in the standard extension for the language (.groovy). The template can be named anything
  2. Have your Jenkins administrator place the script inside JENKINS_HOME\email-templates.
  3. Use the script token with the template parameter equal to your template filename, or in addition the script parameter equal to the custom script name. For example, if the template filename is foobar.template, the email content would look like this ${SCRIPT, template="foobar.template"}.
Template Examples

These are some useful examples for doing various things with the email-ext groovy templates.

jenkins-matrix-email-html.template

Attachments

New to version 2.15 is the ability to add attachments using the Ant pattern matching syntax used in many places in Jenkins. You can set a maximum total attachment size in the global configuration page, or it will be unlimited. 

Jive Formatter

jive-formatter.groovy contains methods for easy and convenient formatting of emails being sent from Jenkins to Jive. It should be called from the Pre-send Script area.

Also, it doesn't seem like Jive supports text with multiple formats, so only call one formatting method per block of text.

Either formatLine or formatText can and should be called on every line of text that will be sent to the Jive system prior to calling formatting methods like color or size. Please test on your own instances of Jive and add functionality as you find it!

The following lines should be added to the Pre-send Script area prior to attempting to invoke any functions.

Pre-send Script
File sourceFile = new File("/your/preferred/path/jive-formatter.groovy");
Class groovyClass = new GroovyClassLoader(getClass().getClassLoader()).parseClass(sourceFile);
GroovyObject jiveFormatter = (GroovyObject) groovyClass.newInstance();

Extend Email-ext

 Make sure you have installed Maven 2 (why?) and JDK 5.0 or later. Make also sure you have properly configured your ~/.m2/settings.xml as explained in the Plugin Tutorial. This is needed to build properly any Jenkins plugin.

Check out and build

How to check out the source and build:

  • git clone git@github.com:jenkinsci/email-ext-plugin.git
  • cd email-ext-plugin
  • mvn clean install

Open Issues

Version History

2.37.2.2 (March 8, 2014)

  • Added caching to the private macros to reduce time (issue #20078)

2.37.2 (January 26, 2014)

  • Marked the Config subclass Extensions as optional, so the plugin doesn't cause issues if the Config File Provider plugin is not installed. (issue #21326)

2.37.1 (January 11, 2014)

  • Fix issue with missing dependency on maven-plugin in  pom.xml

2.37 (January 8, 2014)

  • Updated parent pom version to 1.532.1 LTS
  • Allow use of managed scripts for Jelly or Groovy content. Use prefix "managed:" before name of managed script (issue #18203)
  • Added new "Status Changed" trigger (thanks francois_ritaly)
  • Added fileNotFoundMessage to FILE token (issue #20325)
  • Added inline help for triggers that was missing (issue #20170)
  • Changed BuildStepMonitor.NONE to allow concurrent builds (thanks jglick) (issue #16376)** You must take care when using content or triggers that look at previous builds if you enable concurrent builds for your project
  • Added TRIGGER_NAME token so users can determine what trigger caused the email (issue #20265)
  • Changed to Mutlimap so that you can add multiple triggers of the same type and have them work correctly (issue #20524)
  • Fixed issue where pre-send script would get expanded and remain expanded (issue #20770)
  • Added First Unstable trigger
  • Added helper script for emailing Jive community (thanks Dan Barker)

2.36 (October 26, 2013)

  • Fixed issue with mismatch between form field name and what was parsed in the backend (issue #20133)
  • Fixed issue with NPE on 1.535 (thanks to agudian for the PR)
  • Added ability to customize the date format for the CHANGES_SINCE tokens (issue #20151)
  • Added help files for all the built-in triggers (issue #20170)
  • By default when you add the email-ext publisher, an Always trigger will be added (issue #20013)
  • Fixed issue with template project plugin based jobs and Jelly script content. (issue #20117)
  • If user doesn't have a Mailer.UserProperty, just add the user id and see if the system can resolve it (issue #20215)
  • Fixed issue with newInstance method for EmailTrigger causing an exception on 1.536 (issue #20198)

2.35.1 (October 14, 2013)

  • Fixed issue introduced by new parameter parsing in global config (issue #20030)
  • Update descriptor usage in triggers
  • Fixed command line to not max out PermGen during testing

2.35 (October 12, 2013)

  • Refactored descriptor to follow recommended method
  • Added tests for global config default values
  • Updated to latest LTS for parent version
  • Updated exclusion list to be for full email list, not just committers
  • Fixed issue with email-ext not restoring values for some fields if no triggers were configured (issue #15442)
  • Fixed issue where the project could be null (issue #14338)

2.34 (September 15, 2013)

  • Started adding HtmlUnit tests for UI interaction and round trip testing
  • Added more debug for excluded committers feature
  • Reverted field name to includeCulprits
  • Fixed issue where PROJECT_DEFAULT_RECIPIENTS was being added to triggers (issue #19583)
  • Fixed issue that stopped users from being able to add triggers (issue #19585)

2.33 (September 12, 2013)

  • Fixed issue with triggers for matrix projects not saving the value correctly (issue #19291)
  • Added ability to set content type at the trigger level
  • Added back send to culprits
  • Fixed missing dependency for Mailer plugin in pom.xml
  • Added setting debug mode for JavaMail when debug mode for email-ext is set

2.32 (August 13, 2013)

  • Fix issue with matrix project (issue #19190)
  • Added "Fixed Unhealthy" trigger

2.31 (August 12, 2013)

  • Changed way that triggers work so that you can add multiple triggers of the same type
  • Changed triggers into extension points so that other plugins can provide email triggers
  • Migrated all tokens to use the Token Macro plugin
  • Fixed issue with using template testing with Jelly scripts (issue #18157)
  • General clean-up of sources to remove unused imports and so forth
  • Added JUnit report into groovy html template (thanks praagii)
  • Fixed issue with wrong StringUtils being imported thanks to NetBeans (issue #19089)

2.30.2 (May 23, 2013)

  • Fix issue with escaping tokens by using a more groovy like method (double dollar $$) (issue #18014)
  • Fix issue with metaClass for Script (thanks to Geoff Cummings for patch) (issue #17910)
  • Added ability to test Groovy and Jelly templates via a link on the project page. (issue #9594)

2.29 (May 6, 2013)

  • Refixed typo in email template.
  • Updated to latest LTS release for base (1.509.1)
  • Added global user exclusion list (issue #17503)
  • Added expansion of environment variable in the FILE token's path argument (issue #16716)
  • Added trigger and triggered variables to pre-send script object model (issue #17577)
  • Added DEFAULT_PRESEND_SCRIPT token (issue #14508)
  • Added option to save the output of the generated email into the workspace (issue #13302)
  • Added new trigger for broken -> compiling state (17546)
  • Fixed default value for ReplyTo (issue #17733)
  • Turned off pretty-printing for the CssInliner (issue #17759)

2.28 (April 4, 2013)

  • Fixed token macro help in projects
  • Added additional Chinese translations
  • Improved help text for BUILD_LOG_EXCERPT token
  • Added support for inlining CSS and images into emails
  • Fixed regression in attaching build log (issue #17296)
  • Fixed regression in 1st Failure Trigger (issue #17307)
  • Updated docs for Improvement trigger (issue #17074)
  • Fixed class loading inside Groovy templates (issue #16990))
  • Removed script that created and used template usage
  • Cleaned up unused files

2.27.1 (March 5, 2013)

  • Fix issue with matrix configurations (issue #17064)
  • Add 1st Failure and 2nd Failure Triggers

2.27 (March 2, 2013)

  • Re-added ability to use tokens in attachment areas
  • Allow a default string if regex match is not found for BUILD_LOG_REGEX (issue #16269)
  • Fixed message layout if attachments are present (issue #16281)
  • Added info to the help on using the CC: mechanism
  • Fixed an issue with regression triggers (issue #16404)
  • Added a single retry if a SocketException occurs, in case the network issue was temporary (issue #16181)
  • Fixed attaching build log from a trigger.
  • Made default send to lists less verbose for certain triggers (issue #8642)
  • Added support for personal portions of email addresses ("Some Name" <username@email.com>) including support for unicode
  • Added check of return values from SendFailedException (issue #16919)
  • Made it much easier to use content tokens from groovy templates (issue #16916)
  • Fixed a typo in the html template (issue #16975)
  • Fixed groovy html template when Maven artifacts cause an exception (issue #16983)
  • Include Jacoco output in the default Jelly HTML template.

2.25 (December 12, 2012)

  • Fixed test failures on Mac OS
  • Fixed issue with NullReferenceException if the file doesn't exist for the FILE token (issue #15008)
  • Improved address resolution if the user is setup in the Jenkins system
  • Added a debug mode that will add extra log messages to the build log when enabled in the global config.
  • Updated to core 1.480
  • Added ability to add attachments at the trigger level (issue #13672)
  • Added option to attach the build log at either the project level, or at the trigger level (issue #13848)
  • Improved capture of failed email addresses (issue #16076)
  • Added ability to set Reply-To header value at global, project and trigger level. (issue #3324)* Added ability to set Reply-To header value at global, project and trigger level. (issue #3324)
  • Added parameter (maxLength) to FAILED_TESTS content token to allow truncating the test information. The maxLength is the number of KB allowed (issue #5949)* Added parameter (maxLength) to FAILED_TESTS content token to allow truncating the test information. The maxLength is the number of KB allowed (issue #5949)
  • Added ability to secure the pre-send script by adding a sandbox when enabled in the global config. (issue #15213)

2.24.1 (July 20, 2012)

  • Fixed a few tests which were erroring on Windows.
  • Fixed issue with very long token strings causing SOE (issue #14132)
  • Updated TEST_COUNTS token to include passing tests.
  • Fixed charset issue when using Jelly templates (issue #7997)
  • Allow nested content in JELLEY_SCRIPT tag (issue #14210)
  • Added onlyRegressions parameter to FAILED_TESTS token
  • Allow disable of newlines after each regex match (issue #14320)
  • Removed token macro error messages from logs (issue #9364)
  • Fixed issue when token-macro was older than expected (issue #14224)
  • Fixed changeset author issue with text template
  • Added new trigger for when a job first fails (issue #7859)
  • Allow specifying CC addresses (issue #6703)
  • Updated improvement trigger to only fire if there are failures, but less than previous build (issue #14500)

2.22 (June 15, 2012)

  • Added pre-send groovy script for modifying the MimeMessage and even cancelling the email altogether. (issue #12421)
  • Added support for the token-macro plugin (issue #9364)
  • Added try/catch around user email resolution (issue #13102)
  • Attachment file path now supports content tokens (issue #13563)
  • Fixed issues with tests causing OutOfMemory exception
  • Added BUILD_LOG_MULTILINE_REGEX that allows regexes to match even newlines

2.21 (May 16, 2012)

2.20 (April 12, 2012)

  • Fix issue with hierarchical projects (see [Hierarchical+projects+support|])
  • Updated html_gmail.jelly file to updated fields
  • Updated maven pom to use repo.jenkins-ci.org repository
  • Added scripts for regenerating html.jelly for inline CSS styles
  • Fix issue with Jenkins URL overriding (issue #13242)
  • Fix groovy template for git usage (issue #13192)
  • Fix NPE that causes build to hang (issue #12577)

2.19 ( Mar 24, 2012 )

  • Reimplement default (global) recipient list
  • Fixed default suffix lookup (issue #11731)
  • Added JOB_DESCRIPTION token (issue #4100)
  • Added BUILD_ID token (issue #11895)
  • Groovy template now correctly determines SUCCESS and FAILURE (issue #13191)
  • CHANGES now allows nested content (issue #5376)
  • Fixed NRE when recipientList is not in the saved config (issue #12047)
  • Emails now send when one or more of the recipients is an invalid recipient (issue #9006)
  • Fixed issues with default recipients (issue #11665)

2.18 ( Jan 31, 2012 )

  • Add maximum size limit to ${FAILED_TESTS} (issue #11413)
  • Added improvement and regression triggers
  • Added ${BUILD_LOG_EXCERPT} token (issue #10924)
  • Added emergency reroute option
  • Made compatible with LTS 1.424
  • Email to requester is now correct (issue #9160)
  • Fixed configuration with promoted builds (issue #10812)
  • Only include the stack trace if showStacks is true (issue #3430)

2.16 (Nov 07, 2011)

  • More flexible firing control for matrix projects (issue #8590)
  • E-mail trigger for aborted and "not built" results (issue #10990)

2.15 (Sep 05, 2011)

  • Allow email-ext to attach files to emails (issue #9018).
  • Default Recipients list does not appear in Jenkins global settings(issue #10783).
  • Email to requester uses wrong email address (issue #9160).
  • Allow using Groovy (or other JSR223 languages) to generate the email content.

2.14.1 (Jul 01, 2011)

2.14 (Apr 21, 2011)

  • Improved the portability of the default Jelly templates across different SCM implementations (whereas previously some of the information was only displayed for Subversion)
  • Send the "still unstable" email rather than the "unstable" email, when the previous status was fail, and the status before that was unstable. (issue #5411)

2.13 (Mar 23 2011)

  • Fixed a bug where the html/text Jelly template fail to report the change log correctly for all SCMs but Subversion.
  • If an e-mail is supposed to be sent to the requester, follow the build triggering chain to find the root requester (issue #7740)
  • Added an option to configure a List-ID header on emails.

2.12 (Feb 26, 2011)

  • Rerelease 2.11 to properly set required Jenkins version.

2.11 (Feb 19, 2011)

This version requires Jenkins 1.396 or newer.

  • Added Charset option. (issue #8011)
    • Added "hudson.plugins.emailext.ExtendedEmailPublisher.Content-Transfer-Encoding" system property to specify "Content-Transfer-Encoding".
  • Added "Requester" as possible mail destination (issue #7740)
  • Need tokens to get failed tests count and total tests count, to put them in mail subject easy. (issue #5936)
  • Introduce $JENKINS_URL and deprecated $HUDSON_URL.
  • i18n & l10n(ja)

2.10 (Jan 20, 2011)

  • Added a new content token "FILE" that includes a file from the workspace.
  • BUILD_LOG_REGEX Token:
    • Add escapeHtml - If true, escape HTML. Defaults to false.
    • Add matchedLineHtmlStyle - If non-null, output HTML. Matched lines will become <b style="your-style-value">html escaped matched line</b>. Defaults to null.
  • Prevent duplicate email notifications. (issue #8071)

2.9 (Oct 14, 2010)

  • The showPaths argument was not working for CHANGES_SINCE_LAST_UNSTABLE and CHANGES_SINCE_LAST_SUCCESS. (issue #5486)
  • Add support for custom Jelly script content (JELLY_SCRIPT) (issue #7514)

2.8 (Sept 15, 2010)

This version requires Hudson 1.356 or newer.

  • Update BUILD_LOG_REGEX to properly handle console notes. (issue #7402)
  • Fixed password being saved in plaintext. (issue #5816)
  • Override "Hudson URL" only when "override global settings" is checked. (issue #6193)
  • Add escapeHtml parameter to BUILD_LOG content for escaping HTML. Defaults to false for backwards compatibility. (issue #7397)

2.7 (Aug 30, 2010)

  • New optional arg: ${BUILD_LOG_REGEX, regex, linesBefore, linesAfter, maxMatches, showTruncatedLines, substText} which allows substituting text for the matched regex. This is particularly useful when the text contains references to capture groups (i.e. $1, $2, etc.)
  • Fix invalid illegal email address exception (issue #7057).

2.6 (Jul 20, 2010)

  • Add ${BUILD_LOG_REGEX, regex, linesBefore, linesAfter, maxMatches, showTruncatedLines} token.
  • Add token for build cause. (issue #3166)
  • Add "changes since last unstable build" token. (issue #6671)
  • Fix issue with node properties not being available for the $ENV token. (issue #5465)
  • Recipient list can now use parameters. (issue #6396)
  • Improve docs regarding use of quotes for string parameters. (issue #5322)

2.5 (Jan 20, 2010)

  • Fix issue with adding a pre-build trigger using $BUILD_STATUS would make the build appear as if it was successful or fixed when the build hadn't actually ran yet. (issue #953)
  • Fix NullPointerException when no root URL is configured. (issue #1771)
  • $CHANGES_SINCE_LAST_SUCCESS was not showing unstable or aborted builds in the list of changes since the last successful build. (issue #3519)

2.4 (Jan 7, 2010)

  • Fix bug in 2.3 release that broke saving project config changes if Promoted Builds plugin is not also installed. (issue #5208)
  • Fix in overriding global email settings.
  • Fix to allow authentication without SSL.
  • Send emails as replies to previous ones for same project, as done in Hudson's built-in emailer. (issue #3089)
  • New "Before Build" trigger type. (issue #4190)

2.3 (Jan 6, 2010)

  • Change the token handling to allow for passing of arguments, and allow arguments for the BUILD_LOG, CHANGES, and CHANGES_SINCE_LAST_SUCCESS tokens. (issue #3085)
  • Revamp the help. Now have help on each form element in the config. Rearranged help files hierarchially and deleted unused help.
  • Allow HTML content in emails. There is a global preference plus a per-project preference, which default to plain text.
  • When the emailer can not process an email address, it now prints to the builder output. (issue #1529)
  • Allow use of any environment variable. (issue #3605)
  • Add ability to re-use "global" settings (i.e. settings from the core Mailer configuration)
  • Add support for SVN_REVISION
  • Fix for email triggers with space in name. (issue #3614)
  • Update code for more recent Hudson.
  • Fixed help links. (issue #4566)
  • Compatibility with Promoted Builds Plugin.

2.2.1 (Dec 23, 2008)

Labels

Edit
plugin-notifier plugin-notifier Delete
token-consumer token-consumer Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment