GitHub/Jenkins: Setting up Webhooks
Contents
What is a webhook?
A webhook is a mechanism to automatically trigger the build of a Jenkins project upon a commit pushed in a Git repository.
In order for builds to be triggered automatically by PUSH and PULL REQUEST events, a Jenkins Web Hook needs to be added to each GitHub repository or organization that interacts with your build server. You will need admin permissions on that repository.
This guide details the steps to have Jenkins automatically create a build if it detects changes to a GitHub repository. This can be a very useful improvement to continuous integration setup with Jenkins because this method is only telling Jenkins to attempt a new build when a change is detected rather than polling on an interval, which can be a very inefficient.
For more information, see https://developer.github.com/webhooks/.
GitHub Plugin on Jenkins (only for Jenkins admins)
- GitHub plugin (https://plugins.jenkins.io/github) must be installed on Jenkins. This will give us the ability to configure Jenkins to use our GitHub repository.
Prepare GitHub repository
For each GitHub repository or organization that you need to configure, perform the following steps:
- Navigate to the “Settings” tab.
- Select the “Webhooks” option on the left menu
- Click “Add Webhook”
- For “Payload URL”:
- Use the address for the gCube Jenkins server instance: https://jenkins.d4science.org/github-webhook/
- Make sure to include the last /!
- Select “application/json” as the encoding type
- Leave “Secret” blank (unless a secret has been created and configured in the Jenkins “Configure System -> GitHub plugin” section)
- Select “Let me select individual events”
- Enable Pushes event
- Enable Pull Requests event
- Make sure “Active” is checked
- Click “Add Webhook”
Jenkins will now receive push and pull request notifications for that repository, and related builds will be automatically triggered.
See https://help.github.com/en/github/extending-github/about-webhooks.
Update Jenkins job with GitHub configuration
In the ‘General’ section of the job configuration check the Github project tick box and enter the URL to the repository that you configured in step 2.
Next update the Source Code Management section, first set the repository URL (note the format git@github.com:{YOUR_REPO}. You can also specify the branch you would like to use.
The last step is to tell Jenkins to build when the Github hook is called, select the highlighted option below in the Build Triggers section.
That’s it! Your Jenkins build should now be triggered whenever a push is made to your repository.
Back to the CI guide.
