Official Jenkins plugin · GitHub Enterprise

Trigger Jenkins from GitHub Enterprise without exposing Jenkins

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

One public URL in. One outbound connection out. Nothing else exposed.

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.

    plugins.jenkins.io ↗Source ↗

  • SOC 2 Type II

    Independently audited controls.

    Security details →

Webhooks in, nothing else

GitHub only needs to reach one endpoint. Publishing Jenkins for it exposes every other one.

Exposing Jenkins to GitHub

  • Open an inbound port to the Jenkins controller
  • Allow-list GitHub's webhook source addresses
  • Run and patch a reverse proxy in front of Jenkins
  • Get the firewall change through security review

With the Webhook Relay plugin

  • Jenkins makes one outbound connection
  • Nothing new is reachable from the internet
  • Deliveries are logged and retried for up to 30 days
  • Nothing for the firewall team to approve

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.

Shared secrets keep working

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.

Every delivery logged

Each webhook is stored with the response Jenkins returned, retried for up to 30 days with durable delivery, and replayable from the logs.

Cloud or Server, same setup

Whichever GitHub Enterprise you run, Jenkins only ever connects out.

GitHub Enterprise Cloud

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.

GitHub Enterprise Server

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.

Works with the trigger you already use

Pick the GitHub preset in the plugin. Your jobs stay exactly as they are.

GitHub hook trigger

Freestyle and Pipeline jobs with GitHub hook trigger for GITScm polling, or githubPush() in a declarative pipeline.

Jenkins endpoint

/github-webhook/

GitHub Branch Source

Multibranch pipelines and organization folders. Tick push and pull request events on the webhook to build both.

Jenkins endpoint

/github-webhook/

Generic Webhook Trigger

For custom payload filtering or token-based job selection across many repositories.

Jenkins endpoint

/generic-webhook-trigger/invoke

Also building from Bitbucket or GitLab? Same plugin, same bucket. See the Bitbucket setup

Set up in three steps

Requires Jenkins 2.479.1 or newer. No separate agent to install or keep running.

  1. 1

    Install the plugin

    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

  2. 2

    Add the webhook in GitHub

    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 URL

    Paste this URL into your GitHub/GitLab/Bitbucket/Gitea repository webhook settings:

    https://<id>.hooks.webhookrelay.com

  3. 3

    Push a commit

    The webhook travels from GitHub Enterprise through your bucket to Jenkins, and the build starts. Pull request builds work the same way.

    Jenkins build #1 completed, triggered by a webhook delivered through Webhook Relay
    A real build started by a webhook delivered through the plugin.

Start free, or buy through procurement

Try it on one pipeline

Free$0
150 webhooks a month, enough for a test pipeline
Business$79.99/mo
60,000 webhooks a month, long log retention, priority support

7-day money-back guarantee on paid plans.

Buying for a company?

  • Annual plans paid by invoice and purchase order
  • Help with your security review
  • Vendor onboarding paperwork

Questions

Does this work with GitHub Enterprise Server as well as Enterprise Cloud?

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.

Do I need to allow-list GitHub's webhook IP addresses?

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.

Does the webhook shared secret still work?

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.

What if Jenkins is restarting when a push happens?

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.

Can I run an agent instead of a plugin?

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.

Can we pay by invoice?

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.

Trigger your next build from GitHub Enterprise

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