No inbound ports
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. There is no firewall change for security to approve.
Official Jenkins plugin · GitHub EnterpriseOfficial Jenkins plugin · GitHub Enterprise Cloud · GitHub Enterprise Server
GitHub Enterprise posts every push and pull request to one public Webhook Relay URL. The plugin inside Jenkins
opens an outbound connection and delivers each webhook to /github-webhook/.
No public IP, no allow-listing GitHub's webhook IP ranges, no reverse proxy.
Free plan · No credit card · SOC 2 Type II · Jenkins 2.479.1+
Buying for a company? Talk to sales
Your SCM
GitHub Enterprise Cloud / Server
push, pull_request
Webhook Relay
https://<bucket>
The only public URL. Stored, logged, retried.
Private network · no inbound ports
Jenkins + plugin
→ /github-webhook
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.
GitHub only needs to reach one endpoint. Publishing Jenkins for it exposes every other one.
Exposing Jenkins to GitHub
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. There is no firewall change for security to approve.
Set the same secret on the GitHub webhook and under Jenkins' GitHub settings, as you would for a public Jenkins. Your jobs, branch sources and pull request builds stay exactly as they are.
Each webhook is stored with the response Jenkins returned, retried for up to 30 days with durable delivery, and replayable from the logs.
Whichever GitHub Enterprise you run, Jenkins only ever connects out.
GitHub's servers can't reach a Jenkins on your private network. Instead of publishing Jenkins and allow-listing GitHub's webhook ranges, point the organization or repository webhook at your bucket URL.
When the GitHub appliance and Jenkins sit in different networks (another VPC, data center or cloud), GitHub can trigger Jenkins without a route between them, as long as it can make outbound HTTPS calls.
Pick the GitHub preset in the plugin. Your jobs stay exactly as they are.
Freestyle and Pipeline jobs with GitHub hook trigger for GITScm polling, or githubPush() in a declarative pipeline.
Jenkins endpoint
/github-webhook/Multibranch pipelines and organization folders. Tick push and pull request events on the webhook to build both.
Jenkins endpoint
/github-webhook/For custom payload filtering or token-based job selection across many repositories.
Jenkins endpoint
/generic-webhook-trigger/invokeAlso building from Bitbucket or GitLab? Same plugin, same bucket. See the Bitbucket 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 GitHub preset and save.

Jenkins/Manage Jenkins/System/Webhook Relay
API Key
Concealed
API Secret
Concealed
Bucket name
jenkins-plugin
SCM Webhook Preset
GitHub (github-webhook/)
Connection Status
Subscribed — subscribed to buckets: jenkins-plugin
In the plugin settings, click Get Webhook URL. Then in GitHub, paste it as the Payload URL under Settings → Webhooks, on the repository or the whole organization, with content type application/json.

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 GitHub Enterprise through your bucket to Jenkins, and the build starts. Pull request builds work the same way.

7-day money-back guarantee on paid plans.
Yes. Both send standard GitHub webhooks, and the plugin delivers them to /github-webhook/ like any other GitHub webhook. GitHub Enterprise Server needs to make outbound HTTPS requests to your bucket's public Webhook Relay URL.
No. Nothing connects in to Jenkins. The plugin makes an outbound connection to Webhook Relay, so there is no inbound rule to keep in sync with GitHub's address ranges.
Yes. Set the same secret on the GitHub webhook and in Jenkins under the GitHub section → Advanced → Shared secrets. If Jenkins answers 400 Signature was expected, but not provided, the secret is missing on one side.
Webhook Relay stores the webhook and GitHub 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, paste one URL into your webhook settings, push a commit. Jenkins stays private.
Free plan · No credit card required · 7-day money-back guarantee on paid plans