// troubleshooting guide · jenkins
Jenkins GitHub Webhook Not Triggering Build
- Status
- Workaround available
- platforms:
- Jenkins + GitHub
- updated:
- November 16, 2026
- reports:
- 4
- Method
- how we research
RUNBOOK · jenkins/github-webhook-not-triggering4 FIXES
// quick answer
Check the webhook URL ends in /github-webhook/ and delivers 200, enable 'GitHub hook trigger for GITScm polling', run the job once manually, and make sure the branch specifier matches.
Most likely fix: Check the webhook in GitHub
How to fix it
// try these in order, the most common fix is first
FIX 1Check the webhook in GitHub
- 01Repo > Settings > Webhooks > your hook > Recent Deliveries
- 02Payload URL must be https://<jenkins>/github-webhook/ (with trailing slash), content type application/json
- 03Redeliver and confirm a 200 response
Did this fix it?FIX 2Enable the trigger and build once
- 01Job > Configure > Build Triggers > tick GitHub hook trigger for GITScm polling
- 02For pipelines add triggers { githubPush() } if you define triggers in the Jenkinsfile
- 03Click Build Now once so Jenkins registers the job
Did this fix it?FIX 3Read the hook and polling logs
- 01Open the job page > GitHub Hook Log
- 02Open Git Polling Log and look for errors such as missing ssh or credentials
- 03Fix the error and push again
Did this fix it?FIX 4Match the branch specifier
- 01Job > Configure > Source Code Management > Branches to build
- 02Set it to the branch you push (e.g. */main) or ** for all branches
Did this fix it?
SANDBOX · jenkins RUNS IN YOUR BROWSER
Try it: push, review, run CI and merge in a code host and cloud workspace
A hands-on Jenkins-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.
Symptoms
You push to GitHub, the webhook shows a successful delivery (often 200 OK), but no Jenkins build starts. The job's GitHub Hook Log may say 'Polling has not run yet'.
Why it happens
- C-01The job has never been built, so Jenkins hasn't registered it for hook-triggered polling
- C-02The trigger 'GitHub hook trigger for GITScm polling' isn't enabled
- C-03The branch specifier doesn't match the pushed branch
- C-04Wrong payload URL or Jenkins not reachable from GitHub
- C-05Polling fails on the controller (e.g. missing git/ssh) so no change is detected
// this guide also covers
- jenkins github webhook not working
- jenkins not building after push
- github hook trigger for gitscm polling not working
- jenkins webhook 200 but no build
Still not working?
If Jenkins keeps failing, you're not alone. See every Jenkins problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Jenkins errors
- Jenkins Build Stuck 'Waiting for Next Available Executor'
- Jenkins Build Stuck and Won't Abort
- Jenkins Plugins Failed to Load After Update
- Jenkins Not Starting: 'Job for jenkins.service failed'
- Jenkins java.lang.OutOfMemoryError: Java Heap Space
- Why Is Jenkins So Slow?
- Jenkins 'Scripts Not Permitted to Use Method' Error
- Jenkins Git 'Failed to Connect to Repository' Status Code 128