Figure 8.3. Configuring email notification triggers
You can set up as many (or as few) triggers as you like. The recipients list and message template can
be customized for each trigger—for example, by using the Still Failing and Still Unstable triggers, you
can set up a notification strategy that only notifies developer having committed changes the first time a
build job fails, but proceeds to notify the team leader if it fails a second time. You can choose to send
the message only to the developers who have committed to this build (“Send to committers”), or to also
include everyone who has committed since the last successful build. This helps ensures that everyone
who may be involved in causing the build to break will be notified appropriately.
You can also customize the content of the message by clicking on the More Configuration option (as
shown for the Still Failing trigger in Figure 8.3, “Configuring email notification triggers”). This way,
you can customize different messages to be sent for different occasions.
The triggers interact intelligently. So if you configure both the Failing and the Still Failing triggers, only
the Still Failing trigger will be activated on the second build failure.
An example of such a customized message is illustrated in Figure 8.4, “Customized notification
message”.