This line was removed.
This word was removed. This word was added.
This line was added.
Changes (5)View page history
|By default, as of this writing, Jenkins’s email notifications are fairly basic. It will notify either a specified list of recipients or “culprits” when a build fails. It will contain a generic subject and message, basically indicating that a build failed, but with no details.|
|h21. The Email Extension Plugin: What it gets you|
The Email Extension Plugin will enable you to control the content of the subject and message to make them more meaningful, in addition to the more granular controls I mentioned above.
|Here’s what your “Configure Project” screen will look like once you install the plugin: !hudson_editableemailnotification.png|thumbnail!|
|Notice from this screenshot how you can add notifications on different triggers: “Unstable”, “Still Failing”, etc. You can specify who should receive messages for all of the available events. You can add a new event by selecting one of the available options in the “Add a trigger” Select list.|
|With these variables, on the events I have specified, I get to see what tests have failed and what code changes have happened since the last build. Other variables are available to you. As per Jenkins’s conventions, simply click on the \(?) icon beside the configuration to get all the details for how to use the plugin. Here’s a sample of what you currently get in the Help: !hudson_editablenotification_help.png|thumbnail!|
|h1. My Take|