{"id":135,"date":"2019-03-14T10:27:00","date_gmt":"2019-03-14T10:27:00","guid":{"rendered":""},"modified":"2026-01-08T12:25:21","modified_gmt":"2026-01-08T06:55:21","slug":"can-you-integrate-a-github-webhook-with-privately-hosted-jenkins-no-think-again","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2019\/03\/14\/can-you-integrate-a-github-webhook-with-privately-hosted-jenkins-no-think-again\/","title":{"rendered":"Can you integrate a GitHub Webhook with Privately hosted Jenkins No? Think again"},"content":{"rendered":"
\n
\n
\n
\n
Introduction<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n

Triggering Jenkins builds automatically after every code commit is a core requirement in any continuous integration setup. Jenkins supports automated triggers through repository polling or event based notifications. While polling works, it consumes resources and introduces delays. Push based triggering through webhooks is far more efficient.<\/p>\n

The difficulty appears when Jenkins is hosted inside a private network and the version control system is hosted on a cloud platform such as GitLab. In this scenario, GitLab cannot directly reach the Jenkins endpoint, making webhook based triggering difficult without exposing Jenkins publicly.<\/p>\n

Webhook Relay solves this problem by acting as a secure bridge between GitLab and a privately hosted Jenkins server. This article explains how GitLab webhooks can trigger Jenkins jobs using Webhook Relay, based on real implementation experience.<\/p>\n

<\/p>\n

Installing the Webhook Relay Agent<\/h2>\n

The Webhook Relay agent needs to run on the same machine where Jenkins is hosted or where Jenkins is reachable internally.<\/p>\n

Below is the installation process shown as step based instructions.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
# download the relay binary<\/span>
\ncurl -sSL https:\/\/<\/span>storage.googleapis.com\/webhookrelay\/<\/span>downloads\/relay-linux-amd64 > relay<\/code><\/code># make the binary executable<\/span>
\nchmod +x relay<\/p>\n

<\/code><\/code># move it to a directory in system path<\/span>
\nsudo mv relay \/usr\/<\/span>local\/bin\/<\/span>relay<\/p>\n<\/div>\n<\/div>\n

Webhook Relay service runs on a public endpoint, while this agent runs locally and listens for forwarded webhook events.<\/p>\n

Creating a Webhook Relay Account<\/h2>\n

Create an account on the official Webhook Relay platform using the registration page shown below.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
https:<\/span>\/\/my.webhookrelay.com\/register<\/span>
\n<\/code><\/div>\n<\/div>\n

After signing up, access to the Webhook Relay dashboard is provided, where authentication tokens can be generated.<\/p>\n

Authenticating the Relay Agent<\/h2>\n

From the dashboard, create an access token. This generates a key and secret pair.<\/p>\n

Use those credentials to authenticate the relay agent.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
relay login \\
\n-k <\/span><your_token_key<\/span><\/span>> \\
\n-s <your_token_secret<\/span><\/span>>
\n<\/code><\/div>\n<\/div>\n

A successful login message confirms that the agent is connected and ready.<\/p>\n

Creating the GitLab Repository<\/h2>\n

Create a GitLab repository for testing webhook integration. To keep the setup simple, a public repository can be used.<\/p>\n

For reference, assume the repository name is WebhookProject<\/code>.<\/p>\n

Preparing Jenkins for GitLab Webhooks<\/h2>\n

Install the required Jenkins plugins from the plugin manager.<\/p>\n

Navigate through the Jenkins dashboard to install
GitLab Plugin
GitLab Hook Plugin<\/p>\n

Once installed, Jenkins becomes capable of receiving GitLab webhook events.<\/p>\n

Creating the Jenkins Job<\/h2>\n

Create a new Jenkins job and configure it to pull source code from the GitLab repository.<\/p>\n

Enable the option that allows Jenkins to be triggered by GitLab webhooks.<\/p>\n

After enabling this option, Jenkins generates a webhook endpoint associated with the job. It usually follows this pattern.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
http:\/\/<jenkins-host<\/span><\/span><\/span>>:8080\/project\/<job-name<\/span><\/span>>
\n<\/code><\/div>\n<\/div>\n

Example shown for reference only.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
http:\/\/localhost:8080\/project\/webhook-gitlab-test<\/a>
\n<\/code><\/div>\n<\/div>\n

Copy this endpoint, as it will be used in the forwarding configuration.<\/p>\n

Forwarding Webhooks Using Webhook Relay<\/h2>\n

Start webhook forwarding by creating a relay bucket. This bucket acts as a routing channel between GitLab and Jenkins.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
relay<\/span> forward \\
\n<\/span> --bucket gitlab-jenkins \\
\n<\/span> http:\/\/<jenkins-host>:8080<\/span>\/project\/<job-name>
\n<\/code><\/div>\n<\/div>\n

Important note
Do not stop this process. Keep it running in the background.
Open a new terminal tab for further steps.<\/p>\n

Once this command starts, the relay agent generates a public forwarding URL.<\/p>\n

Configuring GitLab Webhook<\/h2>\n

Open the GitLab repository settings and navigate to the integrations or webhook section.<\/p>\n

Paste the forwarding URL generated by Webhook Relay into the webhook URL field.<\/p>\n

For initial testing, SSL verification can be disabled to avoid certificate related issues.<\/p>\n

Save the webhook configuration.<\/p>\n

Testing the Integration<\/h2>\n

Clone the GitLab repository locally and push a new commit.<\/p>\n

\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n
git add<\/span> .
\ngit commit<\/span> -<\/span>m \"test webhook trigger\"
\ngit push origin main
\n<\/code><\/div>\n<\/div>\n

As soon as the push is completed, GitLab sends a webhook event. Webhook Relay receives it and forwards it to the local agent, which triggers the Jenkins job internally.<\/p>\n

You can verify this by checking the Jenkins job build history.<\/p>\n

Viewing Logs<\/h2>\n

GitLab webhook logs can be viewed from
Repository settings
Integrations
Webhook edit section<\/p>\n

Webhook Relay logs are available in the Relay Logs section of the Webhook Relay dashboard.<\/p>\n

Jenkins build logs confirm successful job execution.<\/p>\n

Conclusion<\/h2>\n

Webhook Relay makes it possible to trigger Jenkins builds through GitLab webhooks even when Jenkins is hosted inside a private network. This approach avoids exposing Jenkins publicly while still enabling real time CI automation.<\/p>\n

The same pattern works for GitHub and other webhook enabled platforms. With proper configuration, secure and efficient CI workflows can be achieved in restricted network environments.<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Introduction Triggering Jenkins builds automatically after every code commit is a core requirement in any continuous integration setup. Jenkins supports automated triggers through repository polling or event based notifications. While polling works, it consumes resources and introduces delays. Push based triggering through webhooks is far more efficient. The difficulty appears when Jenkins is hosted inside … Continue reading “Can you integrate a GitHub Webhook with Privately hosted Jenkins No? Think again”<\/span><\/a><\/p>\n","protected":false},"author":159459904,"featured_media":29900,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[1],"tags":[44070,30871489,27998418,768739308,5603054,281597904,768739299,17852159,676319248],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/opstree.com\/blog\/wp-content\/uploads\/2025\/11\/DevSecOps-1.jpg","jetpack_likes_enabled":true,"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pfDBOm-2b","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/135"}],"collection":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/users\/159459904"}],"replies":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/comments?post=135"}],"version-history":[{"count":7,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/135\/revisions"}],"predecessor-version":[{"id":30299,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/posts\/135\/revisions\/30299"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media\/29900"}],"wp:attachment":[{"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/media?parent=135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/categories?post=135"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opstree.com\/blog\/wp-json\/wp\/v2\/tags?post=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}