Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
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:
- A Jenkins pipeline job needs no special configuration; in the Jenkins configuration for a non-pipeline job...
- In General select GitHub project and fill in the Project url.
- In Build Triggers, select "GitHub hook trigger for GITScm polling".
- On the GitHub project, go to the Settings tab on the top.
- Select the Webhooks menu on the left.
- Select "Add webhook" on the top right.
- For the Payload URL, use the URL of the jenkins.eclipse.org project (not job), with
/github-webhook/at the end. - Don't change Content type or Secret or SSL verification.
- For "Which events", leave the default "Just the push event" or customize as desired.
- 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.