Nothing else reachable
Jenkins keeps no public address, so /cli, the script console and the setup wizard, the endpoints behind exploited CVEs like CVE-2024-23897, can't be reached from outside.
Official Jenkins plugin · Bitbucket DC & CloudOfficial Jenkins plugin · Bitbucket Data Center · Bitbucket Cloud
Bitbucket posts each push and pull request to one public Webhook Relay URL. The plugin inside Jenkins connects out and hands each webhook to the trigger you already use. Jenkins keeps no public address, and nobody opens an inbound port.
Free plan · No credit card · SOC 2 Type II · Jenkins 2.479.1+
Buying for a company? Talk to sales
Your SCM
Bitbucket Data Center / Bitbucket Cloud
repo:refs_changed, pullrequest
Webhook Relay
https://<bucket>
The only public URL. Stored, logged, retried.
Private network · no inbound ports
Jenkins + plugin
→ /generic-webhook-trigger
build started
Safe on company infrastructure
Outbound only
No inbound port, no public IP. Works behind NAT and corporate proxies.
What we store
Each webhook and the response Jenkins returned, for delivery logs, retries and replay.
Official Jenkins plugin
Published in the Jenkins plugin index, open source.
SOC 2 Type II
Independently audited controls.
Bitbucket only has to reach a single HTTPS endpoint. Jenkins only has to make an outbound connection.
Exposing Jenkins to Bitbucket
With the Webhook Relay plugin
Jenkins keeps no public address, so /cli, the script console and the setup wizard, the endpoints behind exploited CVEs like CVE-2024-23897, can't be reached from outside.
Put ?token=<job> on each repository's webhook URL. The query string reaches Jenkins unchanged, so one bucket serves every project.
Each webhook is stored with the response Jenkins returned, retried for up to 30 days with durable delivery, and replayable from the logs.
The same setup covers self-managed Bitbucket and the move to Bitbucket Cloud.
Bitbucket lives in one zone, Jenkins in another (an isolated build network, another VPC, a second site). As long as Bitbucket can make outbound HTTPS calls, it can trigger Jenkins without a route between them.
Bitbucket Cloud can't reach a Jenkins on your private network. Point the Cloud webhooks at the same bucket URL, and Jenkins stays where it is. Only the JSONPath expressions change, because the two payloads differ.
Your jobs stay as they are. Webhook Relay only changes how the webhook reaches Jenkins.
Token-based job selection: add ?token=<job> to each repository's webhook URL. One bucket, any number of jobs.
Jenkins endpoint
/generic-webhook-trigger/invokeMultibranch pipelines and pull request builds. Add an internal output with the full URL and the plugin delivers there.
Jenkins endpoint
/bitbucket-scmsource-hook/notifyThe push trigger, unchanged. On Bitbucket Server it is fed by a Post-Webhook rather than a plain webhook.
Jenkins endpoint
/bitbucket-hook/Also building from GitHub or GitLab? Same plugin, same bucket. See the GitHub setup
Requires Jenkins 2.479.1 or newer. No separate agent to install or keep running.
Manage Jenkins → Plugins → search Webhook Relay. Paste your API key and secret, enter a bucket name, choose the Generic Webhook Trigger preset and save.

Jenkins/Manage Jenkins/System/Webhook Relay
API Key
Concealed
API Secret
Concealed
Bucket name
jenkins-plugin
SCM Webhook Preset
Generic Webhook Trigger (generic-webhook-trigger/invoke)
Connection Status
Subscribed — subscribed to buckets: jenkins-plugin
In the plugin settings, click Get Webhook URL and add ?token=<your-job-token>. Then in Bitbucket, open Repository settings → Webhooks, paste it and select push and pull request events.

Jenkins/Manage Jenkins/System/Webhook Relay
Webhook URL
Get Webhook URLPaste this URL into your GitHub/GitLab/Bitbucket/Gitea repository webhook settings:
https://<id>.hooks.webhookrelay.com
The webhook travels from Bitbucket through your bucket to Jenkins, and the job with that token starts. Check the bucket logs for the response Jenkins returned.

7-day money-back guarantee on paid plans.
Yes. The setup is the same as for Bitbucket Cloud, but the payload is different: the branch is at changes[0].ref.displayId, the repository at repository.slug, and a push arrives with X-Event-Key: repo:refs_changed instead of repo:push. Change the JSONPath expressions in your Generic Webhook Trigger job to match.
Bitbucket needs to make outbound HTTPS requests to your bucket's public Webhook Relay URL. Jenkins needs an outbound connection to Webhook Relay. Nothing has to connect in to Jenkins, and Bitbucket and Jenkins don't need a route to each other.
Yes. Give each job its own token and put a different ?token= value on each repository's webhook, all pointing at the same bucket. Or keep one URL for every repository and attach a small Webhook Relay function that picks the token from the repository name in the payload.
Webhook Relay stores the webhook and Bitbucket gets a success response. With durable delivery it is retried for up to 30 days, and any request can be replayed from the logs.
Yes. The relay CLI, Docker image or Kubernetes operator can forward to Jenkins from any machine on the same network, which is useful when you can't install plugins on the controller.
Yes. Annual plans can be paid by invoice and purchase order, and we help with security reviews and vendor onboarding. Use Talk to sales to request a quote.
Install the plugin, add one webhook URL in Bitbucket, push a commit. Jenkins stays private.
Free plan · No credit card required · 7-day money-back guarantee on paid plans