Chapter 5. Configure notifiers

Table of Contents

Configure Email notifier
Configure MSN Messenger notifier
Configure Jabber notifier
Configure Google Talker notifier
The dummy notifier
Configure subscription notifiers

This chapter describes how to configure various build notifiers.

Configure Email notifier

Below properties need to be defined when set up a email notifier. SMTP related settings is global to QuickBuild, and can be configured in System Settings section of the Administration tab.

Title template

Specify Velocity template for title of the notification mail. Two variables are pre-defined: build means current build object, and system means current system object. Click here for detail information on using the velocity template in QuickBuild.

Content template

Specify Velocity template for title of the notification mail. Two variables are pre-defined: build means current build object, and system means current system object. Click here for detail information on using the velocity template in QuickBuild. This property has the following default value:

#parse ("html_notification.vm")

This instructs QuickBuild to load the template named html_notification.vm from the templates sub directory under QuickBuild installation directory.

Files to attach

Specify files to be sent as attachments. Multiple files should be separated by space, and single file path containing spaces should be quoted. If the file path is not an absolute one, it will be considered to be relative to current build's artifacts directory. Also OGNL expression can be included in file path as long as they are encapsulated in ${...}. For example, if you want to attach the build log, just set this property as:

${build.publishDir}/build_log.txt
Additional resource loader path

QuickBuild uses templates sub directory under its installation directory as the default resource loader path when evaluates Velocity template of this notifier. However you can specify additional resource loader paths here by inputing one path per line. If paths specified here is not absolute, they will be considered to be relative to current build's artifacts directory. Also OGNL expressions can be inserted in these paths as long as they are encapsulated in ${...}.