Manual setup of CI jobs and Pipeline webhooks in Bitbucket

This article explains how to manually create the Bitbucket webhooks Gearset needs to run CI jobs and Pipelines.

Gearset usually creates these webhooks automatically. If your Bitbucket permissions or internal security policy prevent Gearset from creating them, you can create them manually using the payload URL shown in Gearset.

You’ll need:

You can check how the webhooks are setup for a CI job from this article.

To set up the webhook for this Pipeline:

After completing these steps, you should see one new webhook in Bitbucket for the Pipeline.

The Pipeline webhook should use the URL provided on your Gearset Pipeline. The URL should include /pipeline.

Gearset needs one webhook to run all CI jobs for the same repository. This is part of Gearset’s webhook pooling behaviour: one repository webhook can trigger the relevant CI job by checking the event type, repository, and branch.

To set up the webhook for CI jobs:

After completing these steps, you should see one new webhook in Bitbucket for CI jobs.

The CI job webhook should use the URL provided in the Gearset CI job setup. The URL should include /continuous-integration-job.

For a repository using both CI jobs and a Pipeline, you should usually have two Gearset webhooks in Bitbucket: Gearset uses webhook pooling, so one Bitbucket CI job webhook can be shared by multiple CI jobs in the same pipeline. If you’re using a Pipeline with multiple CI jobs, you should still open the webhook setup dialog for each CI job in the Pipeline.