Skip to main content

Bitbucket Pipelines

Learn how to get started with Actioner's solution for Bitbucket Pipelines.

Install Bitbucket Pipelines from app directory and start using it by connecting your Bitbucket and Slack accounts.

Features​

Actioner brings your Bitbucket Pipelines as ready-to-use actions in Slack, without any configuration!

  • Running Bitbucket Pipelines in Slack: Get up and running in seconds; no overwhelming configuration or extra effort needed. You can manually run any Bitbucket pipeline right in Slack. As you connect and select your workspace, repository, default branch, the pipelines YAML and your pipeline, your Bitbucket action is automatically generated as a ready-to-use action in Slack.
  • Bitbucket pipeline notifications in Slack: Whenever you run a pipeline, Actioner notifies you with a direct message allowing you to track its progress. You and your teams can also get notified in your preferred channel when a pipeline is triggered and view its live status. Actioner also sends the live status of each individual job that is triggered when the pipeline is triggered. All messages for individual jobs are collapsed under the same thread, allowing you to track all the context in one place.

Get started​

Step 1. Install Bitbucket Pipelines​

Visit this link in app directory and click Install button at top right corner.

Install Bitbucket Pipelines

Step 2. Connect to Bitbucket and Slack​

After installing the app, you'll be prompted to connect your Bitbucket account.

Connect to Bitbucket and Slack

Complete Bitbucket admin connection

  1. Click Connect near Bitbucket admin connection and proceed to authentication in Bitbucket via OAuth2.
  2. You will be asked to sign in to your Bitbucket account if you haven't already.
  3. Click Authorize Actioner. You’ll be redirected to Actioner upon successful authorization.

Complete Bitbucket connection

  1. Click Connect near Bitbucket admin connection and proceed to authentication in Bitbucket via OAuth2.
  2. You will be asked to sign in to your Bitbucket account if you haven't already.
  3. Click Authorize Actioner. You’ll be redirected to Actioner upon successful authorization.

Complete Slack connection

  1. Click Connect near Slack connection.
  2. Continue with selecting your Slack workspace.
Tip

If your workspace is not available, add it by navigating to your workspace from the left menu and then go to Slack connections page and click + Add Slack workspace.

Step 3. Complete setup actions​

Setup Bitbucket Pipelines

  1. Run Subscribe to Bitbucket events action 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 this step, you will start getting direct message notifications whenever you run the selected pipeline in Bitbucket or in Slack. The message contains the live status of the workflow that is triggered and the live status of each individual job in one thread.

    Tip

    Re-run Subscribe to Bitbucket events action multiple times if you want to subscribe events from multiple repositories. Even after you close the setup wizard, you can go to action bar and type Subscribe to Bitbucket events and re-run it. Or call Actioner from shortcuts, or type /actioner in Slack and type Subscribe to Bitbucket events and re-run it.

  2. Run Create action for a pipeline action by selecting your repository and pipeline. This action dynamically generates a new action for the pipeline you select. The new action is generated with the parameters your pipeline requires and becomes available to be run in Actioner and Slack. To run the pipeline in Slack, you can simply call Actioner from shortcuts, or type /actioner, and then type the name of your pipeline.

    Tip

    Re-run Create action for a pipeline action multiple times for any Bitbucket pipeline you'd like to run in Slack. Even after you close the setup wizard, you can go to action bar and type Create action for Bitbucket pipeline and re-run it. Or call Actioner from shortcuts, or type /actioner in Slack and type Create action for Bitbucket pipeline and re-run it.

  3. Run Select channel for pipeline run results action 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. Whenever a selected pipeline is run, by you or another user, in Slack or in GitHub, Actioner sends a notifiction to the selected channel with the result of the pipeline that is triggered. You can view the live status of the triggered pipeline and the live status of each individual job in one thread.

    Tip

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

Step 4. Finish setup guide​

When all steps in setup guide are completed, app is ready to be run in Slack.

Get started as an app user​

If you are invited to this app as a user, you need to complete Zendesk connection. This connection is required for you to take actions on Zendesk notifications in Slack.

  1. Navigate to Zendesk connection, click Connect and proceed to authentication in Zendesk via OAuth2.
  2. You will be asked to sign in to your Zendesk account if you haven't already.
  3. Click Connect app. You’ll be redirected to Actioner upon successful authorization.

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.

  1. Navigate to Bitbucket connection, click Connect and proceed to authentication in Bitbucket via OAuth2.
  2. You will be asked to sign in to your Bitbucket account if you haven't already.
  3. Click Authorize Actioner. You’ll be redirected to Actioner upon successful authorization.

Running Bitbucket Pipelines in Slack​

After completing connection, you can start running Bitbucket Pipelines manually in Slack. To trigger your pipeline manually in Slack, call Actioner from shortcuts, or type /actioner 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.

Bitbucket Pipelines notifications in Slack​

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

  1. Call Actioner from shortcuts, or type /actioner 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 in Slack. 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.
Tip

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

How to customize this app​

Generate different actions to manually run a different Bitbucket pipeline in Slack​

If you are looking to generate additional pipelines available to be triggered in Slack after the setup, or if you are invited to this app as user, follow the below steps:

  1. Call Actioner from shortcuts, or type /actioner in Slack.
  2. Start typing Create action for a pipeline.
  3. Run this action by selecting your Bitbucket workspace, repository, default branch name, the pipelines YAML and your pipeline.

Get notified for different Bitbucket pipeline runs in different Slack channels​

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

  1. Call Actioner from shortcuts, or type /actioner 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.

FAQs​

How to run a Bitbucket pipeline manually in Slack​

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.

Not getting a direct message when I run a pipeline in Slack​

If you don’t receive DM for the pipelines that you have run, please follow the steps described in this documentation.