How to set up Azure DevOps Pipeline triggering from Bitbucket Server?

By integrating Post Webhooks for Bitbucket with Azure DevOps Pipelines, you can achieve tighter integration between your Bitbucket repositories and your CI/CD workflows, enabling seamless automation and ensuring that your code is always up to date and properly deployed.

This guide is for Post Webhooks for the Bitbucket Atlassian Marketplace application.

Getting the personal access token

To move forward with the configuration of Azure DevOps Pipeline triggering, we recommend you first obtain a Personal Access Token (PAT) to connect your Confluence and Azure DevOps instances. You can use a service account to generate this PAT but do remember that Microsoft forces you to log in every 90 days to keep the PATs active.

The following steps will help you create a new Personal Access Token:

1. Navigate to the User Settings in the right corner of the navigation menu.

2. From the drop-down, select Personal access tokens.

3. Click on the New Token button and generate a new personal access token with minimal scope. Currently, the App needs the token to Read access to the builds.

Alternatively, you can use this official guide from Microsoft.

Configuration

Once you have got the Personal Access Token, you can proceed with the configuration of Azure DevOps Pipeline triggering. Configuration of Azure DevOps Pipeline triggering is available on all configuration levels:

Global Configurations for Bitbucket admins

Project Level Configurations

Repository Level Configurations

1. Find our application Post Webhooks on the level that suits your needs best: Global, Project, or Repository.

2. Click on Add webhook button in the left corner and create a new configuration.

3. Tick the checkbox Trigger Azure DevOps pipeline and specify all the necessary parameters.

4. After you have specified all the necessary parameters click on the Save button.

Below you can find a short definition of the parameters you have to specify:

Parameter	Definition
Title	the name of the configuration Our advice is to name something meaningful to you and your team so that it can be understood later easier
Trigger Azure DevOps pipeline	allows you to specify the Azure DevOps pipeline that should be triggered when the webhook event occurs.
URL	a link to the pipeline by pattern: Cloud - https://dev.azure.com/{ORG_NAME}/{PROJECT_NAME}/_build?definitionId={PIPELINE_ID}; Server - https://yoursever/{COLLECTION}/{PROJECT_NAME}/_build?definitionId={DEFINITION_ID}.
Azure source	specifies where the target pipeline is located: Cloud; Server.
Personal Access Token	the personal access token (PAT) used for authentication with Azure DevOps.
Target Azure DevOps Branch	the branch in the Azure DevOps repository where the pipeline to be triggered is located.
Parameters to send	additional parameters or variables that need to be passed to the Azure DevOps pipeline when triggering it.
Status	Active checkbox should be enabled if this configuration is going to be used.
Repository events Pull request events	allows you to specify the types of events that should trigger the pipeline.

The rest parameters are optional to provide flexibility and customization options to tailor the webhook integration according to your specific needs.

Azure DevOps pipeline parameters

If you want to update the build status in Bitbucket from the Azure DevOps pipeline, you may need to use some defined parameters. For some Bitbucket events, some parameters are not available and as a result, they are not sent to the Azure DevOps pipeline.

Please, make sure that the parameters of the pipeline are settable at the queue time.

Follow this guide from Microsoft and check out our short video explainer.

The following parameters are passed to the pipeline when it is triggered:

Demo Video

Updated: 20 Jun 2023