System level notifications

Still need help?

The Atlassian Community is here for you.

Ask the community

robotsnoindex
robotsnoindex
robotsnoindex

Error rendering macro 'viewport-redirect'

null

System level notifications in Bamboo are triggered by a small range of system level events. This means that you don't need to configure these notifications for each plan you are running, as they are applied globally across the Bamboo platform.

Recipients receive notifications by email and, in general, do not require Atlassian Cloud user accounts. Note that notifications can not be received by IM – see  Restricted functions.

 

On this page:

Add system level notifications

  1. Unable to render {include} The included page could not be found.
  2. Select System notifications to display the System notification configuration screen
  3. Click Add notification to add a new notification:
  4. Complete the Event and Recipient type fields using the following table:

    SettingNotes
    Event Type

    Job Hung Bamboo will send a notification whenever it determines that one of the plan's job builds has hung, according to the hung job build criteria (read more about configuring your hung job build settings).
    (tick) Use this notification to ensure that the relevant people are informed when a job build becomes unresponsive.
    Job queued without capable agents Bamboo will send a notification whenever one of the plan's job builds is queued and there are no agents capable of building it.
    (tick) Use this notification to ensure that people are notified when changes to agents adversely affect your job's builds.
    Job queue timeout Bamboo will send a notification whenever one of the plan's job builds has been waiting in the queue for longer than the build queue timeout criteria (read more about configuring your job's Build Queue Timeout settings).
    (tick) Use this notification to ensure that the relevant people are informed when a job build is stuck in the build queue for too long.
    Recipient TypeUser — Enter the username of the appropriate Bamboo user, or click the icon to select from a list of users.

    Hipchat — Enter the Hipchat API Token and Room Name. See Integrating Bamboo with HipChat for more information.

    Group — Enter the name of the appropriate Cloud group(s).

    Email Address — You can use email to send notifications to a person who is not a Bamboo user. Type the appropriate email address. Note that:

    • If you specify the email address of an existing Bamboo user, the user will receive notifications even if they have elected not to receive notifications in their user preferences.
    IM Address— This is useful if you need to send Instant Messenger (IM) notifications to a person who is not a Bamboo user. Type the appropriate IM address. Note that:
    • If you specify a broadcast address (eg. 'project-x@broadcast.chat.mycompany.com'), Bamboo will not know the context of relatedIM responses.

    • If you specify the IM address of an existing Bamboo user, the user will receive notifications even if they have elected not to receive notifications in their user preferences.
    Responsible Users — The Bamboo users who have been assigned as being responsible for a broken build. See Assigning responsibility for build failures.
    Committers — The Bamboo users who have committed code to a particular build since build was last checked out by Bamboo.
    Watchers — The Bamboo users who have marked this plan as one of their favorites.
  5. Click Add to confirm your configuration.

Change system notifications

  1. Unable to render {include} The included page could not be found.
  2. Select System notifications:
  • Click the pencil symbol in the Actions column to edit the notification.
  • Click the cross symbol in the Actions column to remove the notification.

 

Last modified on Feb 11, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.