Page History

...

Everything related to Jenkins

GitHub webhooks

Note : Github webhook for apache/incubator-mxnet can only be created by the Apache Infra team. A request needs to be made for setting up a new webhook / updating existing webhook. For ex :

GitHub webhooks allow to be notified of GitHub events instead of polling. This allows us to operate without running into rate limiting. The configuration in Jenkins has a few catches that can save you quite some time:

Create a webhook at https://github.com/ACCOUNT/REPOSITORY/settings/hooks/. You can use this configuration for reference:

Note : Make sure to include the trailing `/` in the Payload URL section for configuring the webhook on Github. Refer : 302 Github webhook with Jenkins error on StackOverflow.

You will have to create a secret manually. Note it down as it is required to be entered into Jenkins.

...

On "Shared Secret", press "Add". A new window will open up. In the "Kind" dropdown, select "Secret text". Then input something like the following and insert the previously noted down secret:

Now go back to the GitHub webhook and press "Redeliver":

...

Here you can see, for example, that the PR did not contain the requested file. In this particular case, the background was a bit different. See the guide below for details

Jenkinsfile not found or changes not reflected

If you create a new Jenkinsfile and it does not get picked up by Jenkins with the following message if you submit a pull request

Checking pull request #5
  ‘ci/jenkins/Jenkinsfile’ not found
Does not meet criteria

this might not mean that the file . is missing but rather be related to the security restrictions Jenkins has. The background here is the fact that Jenkins does not evaluate Jenkinsfiles from people without write permissions to the repository. Request somebody with write permissions to open the pull request instead.

GitHub commit/PR status does not get published 

...