Overview
A email committers post build action can be used to send a notification email to users that committed changes that affected the build. This is an alternative to the subscription system that is available to all pulse™ users to configure their own notifications. The advantage of this post build action is the ability to notify committers that either do not want to configure their own subscriptions or do not have pulse™ accounts. It is also a simple way to get started with notifications, allowing users to then customise their preferences as they choose later if desired.
To send these emails, pulse™ needs to map between login names in the project SCM and email addresses. Currently this is done by assuming that the SCM login names and email ids are identical. This allows you to configure the email addresses by providing just the email domain, which pulse™ will append to the SCM login (with an "@" in between) to form email addresses.
Configuration
email domain
The domain to send notification emails to. This domain is joined to the committer logins (obtained from the SCM) with an "@" symbol to form email addresses. So, for example, if the SCM reports that users "jsmith" and "pdexter" committed changes, and the domain is set to "example.com", emails will be sent to "jsmith@example.com" and "pdexter@example.com".
This field is required.
examples
template
Defines the template that will be used to render the build result. For example, you can choose HTML or plain text emails. For more information about templates, see the Subscription Templates page.
ignore pulse users
If checked, users with pulse™ accounts will not be notified by this mechanism. This allows subscriptions by pulse™ users to take precedence over this mechanism. Users with pulse™ accounts are found by matching the SCM logins with pulse™ logins.
