Disable/Enable Bitbucket Trigger for Azure DevOps Pipeline

When you create new pipeline for Bitbucket repository in Azure DevOps Pipeline it will automatically create a webhook integration in the Bitbucket for you. That’s the reason you should be administrator on Bitbucket repository when you want to setup pipeline.

It can be broken when somebody deletes these webhooks. Unfortunately, it won’t work silently.

It is no easy to re-initiate it, because the webhook URL contains a channelId that I don’t know where comes from.

The webhook URL looks like this:

https://dev.azure.com/{Your DevOps organization}/_apis/public/hooks/externalEvents?publisherId=bitbucket&channelId={channelId for your integration}&api-version=6.1-preview

For these things, there is a hidden or unknown settings page for YAML pipeline too.

Triggers menu in Edit pipeline

On this page you will see something is broken.

How to restore a CI or PR trigger (webhook) for pipeline

1. Edit the Pipeline
2. Open the menu (three dots menu in right side)
3. Click on the Triggers menu item
4. Click on the CI or PR trigger
5. Click on the Restore button.

It will re-create the webhook for you.

Restore pipeline webhook

How to disable a CI or PR trigger without a YAML change

Of course, you can disable trigger in YAML with

trigger: none

but there are some tricky situations when you need more.

In this case the Triggers menu is your friend.

1. Edit the Pipeline
2. Open the menu (three dots menu in right side)
3. Click on the Triggers menu item
4. Click on the CI or PR trigger
5. Click on the Restore button.

Disable CI trigger on the UI