This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

You can specify which people will receive notifications about build results for a particular plan, and under what circumstances (known as 'Notification Triggers'), i.e.:

Notification Trigger

Description

'All Completed Builds'

Bamboo will send a notification whenever a build finishes for this plan, regardless of the build result. This trigger is recommended for any plans for which it is critical that people are always informed about the latest build activity.
Many organisations start with this trigger, then change it later as they get more confidence in the continuous build process.

'Failed Builds And First Successful'

Bamboo will send a notification whenever:

  • a build fails for this plan.
  • the plan is 'fixed' (that is, the plan's latest build is successful and the previous build failed).This trigger is generally suitable for the majority of plans.

After X Failed Builds'

This trigger enables you to specify the 'Number Of Failed Builds' after which Bamboo will send a notification. This is a useful way of limiting the number of notifications, if you are concerned about people receiving too many.

For each plan, you can specify different recipients for each Notification Trigger. Note also that recipients need not be people with Bamboo user accounts.

Before you begin

You need to configure Bamboo's system email and/or instant messaging capabilities before Bamboo can send notifications.


To enable notifications for a plan,

  1. Click 'Home' to go to the Dashboard.
  2. Click the 'All Plans' tab.
  3. Locate the plan in the list and click this icon:
  4. The 'Configuration' tab will be displayed. Click the 'Post Actions' tab.
  5. A list of 'Notification Triggers' will be displayed. Select the 'Notification Trigger' you wish to enable, then specify any or all of the following recipients:
    • 'Roles' — Select from the following:
      • 'Committer' — The Bamboo user(s) who have committed to this build (i.e. users who committed code after the previous build was checked out by Bamboo).
      • 'Watcher' — All Bamboo users who have marked this plan as one of their favourites.
    • 'Groups' — Type the names of the appropriate Bamboo group(s), separated by commas.
    • 'Users' — Type the usernames of the appropriate Bamboo users, separated by commas; or click the following icon to select from a list of users:
    • 'Email Addresses' — This is useful if you need to send email notifications to people who are not Bamboo users. Type the appropriate email addresses, separated by commas.
    • 'Instant Messaging Addresses' — This is useful if you need to send IM notifications to people who are not Bamboo users. Type the appropriate IM addresses, separated by commas. Note that if you specify a broadcast address (eg. 'project-x@broadcast.chat.mycompany.com'), Bamboo will not know the context of related IM responses.
  6. Click the 'Add' button.
  7. Repeat steps 5 and 6 until you have added all the Notification Triggers that you wish to enable for this plan.
  8. Click the 'Done' button.

(info) Each Bamboo user can choose whether to receive their notifications via email, IM, both or neither.


Screenshot: 'Plan Configuration-Post Actions' 







To disable notifications for a plan,

  1. Click 'Home' to go to the Dashboard.
  2. Click the 'All Plans' tab.
  3. Locate the plan in the list and click this icon:
  4. The 'Configuration' tab will be displayed. Click the 'Build Notifications' tab.
  5. For each 'Notification Trigger', click the corresponding 'Remove' link in the 'Operations' column.
  6. Click the 'Done' button.
     

Bamboo will no longer send notifications about this plan's build results.





















RELATED TOPICS


















Bamboo Documentation



























  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.