Skip to main content
Jump to: navigation, search

GitHub Webhook Configuration

A GitHub Webhook can be used to trigger a Jenkins job when a GitHub repository changes. For example, you can trigger a build when changes are pushed to the repository.

Here's how to configure a Webhook:

  1. A Jenkins pipeline job needs no special configuration; in the Jenkins configuration for a non-pipeline job...
    1. In General select GitHub project and fill in the Project url.
    2. In Build Triggers, select "GitHub hook trigger for GITScm polling".
  2. On the GitHub project, go to the Settings tab on the top.
  3. Select the Webhooks menu on the left.
  4. Select "Add webhook" on the top right.
  5. For the Payload URL, use the URL of the project (not job), with /github-webhook/ at the end.
  6. Don't change Content type or Secret or SSL verification.
  7. For "Which events", leave the default "Just the push event" or customize as desired.
  8. Click "Add webhook" to complete.

Under the Webhook configuration you can see the delivery attempts. Note that redelivering a successful Webhook event will not cause the job to be run again. It seems that the only way to test a Webhook is to make a change to the repository.

Back to the top