Bitbucket is the Git solution for professional teams. Bitbucket core features include pull requests, branch permissions and inline comments. With the Bitbucket integration for PagerDuty, you can notify on-call engineers about failures within your Bitbucket pipelines.
This integration is intended for Bitbucket cloud.
Within your PagerDuty account, a Custom Event Transformer needs to be created. This allows PagerDuty to process webhooks from your Bitbucket account. Each repository in Bitbucket can send failure information to different PagerDuty Services. Determine which Bitbucket repository and PagerDuty service you would like to integrate.
- Go to Services Service Directory
- Select the PagerDuty service you wish to integrate with, then go to the Integration tab.
- Click Add a new integration.
- Provide a title for the integration, such as "Bitbucket". From the Integration Type drop down, search for Atlassian Bitbucket Pipelines, then press Add Integration.
- You will be taken back to the Integrations tab showing the newly added integration. Click the name of the Atlassian Bitbucket Pipelines integration you created above.
- From this screen, copy the Integration URL value. This will be needed when you configure webhooks in your Bitbucket account.
The remaining configuration resides on the Bitbucket side, through the Bitbucket user interface. You will be adding webhooks that will send failure information to PagerDuty.
- Open the repository you want to integrate with PagerDuty. From the left side navigation, open Settings.
- Click Webhooks from the Workflow sub-heading, followed by Add Webhook.
- Provide a title, then paste the PagerDuty URL you copied from the above steps.
- Change the Triggers radio option to Choose from a full list of triggers.
- Under Repository, select Build status updated
- Save the configuration.
You have successfully completed setting up the integration. When there is a failure in your pipelines, a PagerDuty incident will notify on-call responders. When the failure recovers, a SUCCESSFUL message is sent to PagerDuty and the PagerDuty incident will be automatically resolved.
Updated about a year ago