Check out the main features and capabilities of the Post Webhooks for Bitbucket app.
Post Webhooks for Bitbucket application for Bitbucket On-Premise (Server and Data Center) streamlines integration of Bitbucket and Jenkins, Azure DevOps, Microsoft Teams and many other tools:
allows to send JSON payloads to external systems like Jenkins, customer scripts, and serverless functions.
lets to configure the HTTP method to be used when sending webhook requests: POST (default), PUT and GET (not HTTP body sent), which ensures flexibility in how you receive and handle webhook payloads;
provides support for Azure DevOps Pipelines (Cloud and Server) that allows you to trigger Azure DevOps pipeline runs based on events occurring in your Bitbucket repositories;
users can configure global, project, and repository webhooks: the app supports multiple configurations per level for project and repository configurations or only one configuration on a global level; this parameter can be changed;
the app also supports Mutual TLS and allows users to filter events using various criteria, including event type, committers, repository and branch masks, and from/to branches.
sends Microsoft Teams real-time notifications to Microsoft Teams channels whenever certain events occur in Bitbucket repositories. With this integration, you can configure a webhook in Bitbucket to send a payload to a Microsoft Teams Incoming Webhook URL whenever a specific event, such as a code push or a pull request merge, takes place.
support of Basic, Bearer and Kerberos authentication to ensure secure communication when sending webhook requests.
you can use API to create rules. The API allows you to automate the creation and management of webhook rules, making it easier to configure and maintain your webhook integrations. The Bitbucket Branch Source Jenkins plugin uses the same APIs.
users can also include query string parameters in their requests;
the app has the option to skip SSL and URL validations and to skip notifications for personal projects and repositories.
Query string parameters support
Query string parameters support allows the passing of additional information or configuration settings to the webhook URL when a webhook event occurs.
The following query string parameters are supported:
the repository slug.
the project key.
the branch name.
the from branch name of the pull request (relative git path) - f.e. refs/heads/bug/someBug
the from-branch name - f.e.
the to-branch name of the pull request (relative git path) - f.e. refs/heads/master
the to-branch name - f.e.
the pull request url
Build status event handling
Bitbucket build status API provides the only commitId and Bitbucket Post Webhooks needs to find rules to process an event. Because the App cannot get repository information, it uses two approaches to find the repository by commit id:
Default: the app caches the commit id and repository id to find the repository id by commit id in O(1) time.
Disabled by default since 3.12.23.
Repository search: the app scans all repositories and projects, globally where rules exist with
Enable repositories scan for build statusparameter switched on on Global settings tab. This approach is not very performant when a huge repository because it results in a repository scan.
Enabled by default before 3.12.23.