Webhook URLs must reach the Webhooks service (port 3332). Using the API domain only works if your reverse proxy routes
/.../webhook paths to the webhooks service.- Navigate to your Bitbucket repository
- Click on “Repository settings” in the left sidebar
- Select “Webhooks”
- Click “Add webhook”
-
Time to configure your webhook:
- Title: Kodus Code Review
- URL: Drop in the URL where you want to receive notifications, the URL you put under
GLOBAL_BITBUCKET_CODE_MANAGEMENT_WEBHOOKin the.envfile - Status: Active
- SSL/TLS: Check Enable SSL verification
- Triggers: Select these events:
- Pull Request
- Created
- Updated
- Merged
- Declined
- Comment created
- Pull Request
- Click “Save”
Kodus only consumes Pull Request events —
created, updated, merged, declined, and
comment created. Repository, Issue, and build-status triggers are discarded on arrival, so
leaving them unchecked keeps the webhook traffic down.On Bitbucket Data Center the equivalent events are pr:opened, pr:modified,
pr:reviewer:updated, pr:comment:added, pr:merged, and pr:declined.