Bitbucket Pipelines notifications in Slack

What's it for

Keep everyone up-to-date with automated notifications when a pipeline runs, track progress in your preferred Slack channel and easily identify where failures and slowdowns occur.

How it works

Integrating Bitbucket Pipelines and Slack seamlessly, Actioner brings smart notifications to Slack. You can get updated with smart notifications when a Bitbucket pipeline runs and track successful, failed, and in-progress runs in your preferred Slack channel and pinpoint where errors, failed codes and slowdowns take place.

Actioner allows you to select your preferred channels to get updates on different Bitbucket pipeline statuses. It also sends a direct Slack message whenever you trigger a pipeline, whether in Bitbucket or in Slack. Without leaving Slack, you can see the progress of your pipeline runs and track the live status of each individual job in one place under the thread message showing the status of the triggered pipeline.

How to get started

To begin using Bitbucket Pipelines in Slack,

1. Sign up to Actioner.
2. Install Bitbucket pipelines.
3. Connect to Bitbucket and Slack.
4. Run the setup action named Subscribe to Bitbucket events by selecting your Bitbucket workspace and repository. This action creates a webhook on Bitbucket and subscribes to the commit events of the selected repository. After running it, you will start getting direct message notifications whenever you run the selected pipeline in Bitbucket or in Slack.
   
   💡If you want to subscribe events from multiple repositories, you can re-run this action.
   ‍
5. Run the setup action named Select channel for pipeline run results by selecting your Bitbucket workspace, repository, Slack channels and the events you want to get notified of. Available event types are build in-progress, build succeed and build failed. This action subscribes to the selected events in the selected repo and sends notifications to selected Slack channels for these events.
   
   💡If you want to get notifications for different events in different channels, you can re-run this action.

If you are looking to manually run your pipelines in Slack, visit Running Bitbucket Pipelines in Slack page.

If you are looking to generate additional pipeline notifications in different Slack channel after the setup, follow the below steps:

1. Call Actioner app in Slack.
2. Start typing Select channel for pipeline run results.
3. Run this action by selecting your Bitbucket workspace, repository, Slack channels and the events you want to get notified of. Available event types are build in-progress, build succeed and build failed. This action subscribes to the selected events in the selected repo and sends notifications to selected Slack channels for these events.

💡If you want to get notifications for different events in different channels, you can re-run this action.

How to get started as an app user

If you are invited to use this app with your colleagues, you only need to connect your Bitbucket account by granting access to Actioner. After connecting, you’ll start getting notifications as direct messages whenever you run a pipeline, whether in Bitbucket or in Slack. More than that, you can track the live status of your pipelines in Slack and the live status of each individual jobs in one place under the thread message showing the status of the triggered pipeline.

To trigger your pipeline manually in Slack, simply call Actioner app and type the name of your pipeline. Actioner will automatically suggest the action that will trigger your pipeline.

On the opening screen, enter the parameters to run your action. These parameters are the ones you provide to run the same pipeline manually in Bitbucket. They are dynamically generated from the YAML file of your pipeline. You can run your action in Slack-with the same parameters you trigger the selected pipeline manually in Bitbucket.

If you are looking to get notified of different pipeline statuses in different Slack channels, follow below steps:

1. Call Actioner app in Slack.
2. Start typing Select channel for pipeline run results.
3. Run this action by selecting your Bitbucket workspace, repository, Slack channels and the events you want to get notified of. Available event types are build in-progress, build succeed and build failed. This action subscribes to the selected events in the selected repo and sends notifications to selected Slack channels for these events.

💡 If you want to get notifications for different events in different channels, you can re-run this action.

If you are looking to manually run your pipelines in Slack, visit Running Bitbucket Pipelines in Slack page.