Notifications for Bitbucket Pipelines

Bitbucket Pipelines can send notifications to your team's chat room, and to your email.

See also:

Chat notifications

Slack

Pipelines can notify Slack about pipeline and deployment results, repository wide, or only for specific branches in addition to the existing Bitbucket notifications.

If you had the legacy integration app installed, you will want to remove it first to avoid duplicate notifications.

Install the Slack app

  1. Open the repository you wish to configure notifications for.
  2. Click Settings then select Chat notifications > Settings.
  3. Press the Connect button under Slack. A dialog for Slack login might open if you are not already logged in.
  4. Choose the Slack workspace to connect to your repository.

You should receive an automated welcome message in Slack.

Then you can choose which notifications to receive, in the repository specific settings. Notifications can be configured for the whole repository or on a per-branch basis.

  1. Open one of the repositories you have connected to Slack.
  2. Click Settings then select Chat notifications > Settings.
  3. Select the down arrow to the right of the relevant branch, or add a new one if needed.
  4. Choose the notifications to receive.
    Note: It can be helpful to set notifications on a per-branch basis. For example, it may be important to receive pipeline fixed notifications for your master branch, but not for other branches in the repository.

For Pipelines we have the notifications:

  • pipeline succeed
  • pipeline failed
  • pipeline fixed (for a successful completion after a failed attempt)
  • deployment succeeded
  • deployment failed (this includes error states)
  • deployment stopped (including paused due to concurrency)

The default configuration is shown here:

Image of default notifcation setting

Note: build failed and build succeeded are for external third party build tools and do not include Bitbucket Pipeline notifications.

If you receive failed pipeline notifications in Slack, you can re-run your failed build from within your Slack channel.

an image of a hopeful but failed pipeline

Hipchat

It's easy to get Pipelines to notify Hipchat rooms about build result successes and failures:

Read more about setting up notifications for Hipchat.

Email notifications

You can get emails about:

  • when you push and the pipeline fails.
  • all failed pipelines in a repository.

If you provided your email in the Bitbucket settings for your account, you'll get notified each time your push triggers a pipeline that fails:

Currently, you can unsubscribe from notifications by following the steps in Enabling or disabling email.

Manual steps and notifications

Pipeline completion notifications are sent when there are no further steps that can be run in the pipeline. This means notifications are sent when:

  • the initial automated steps in the pipeline are complete, even if later manual steps remain to be run
  • when a manual step (and any following automated steps) completes, even if later manual steps remain to be run.

This is designed to cover the primary use case of manual steps being used for deployments, where the team should be notified about deployments.

Some notification channels (e.g. HipChat) allow filtering of build status, which can be used to further filter notifications from manual steps.


Generic webhooks

You can set up notifications for other services by creating webhooks.

You can add the following webhooks specific to Pipelines:

Last modified on Aug 30, 2018

Was this helpful?

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