THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Now go back to the GitHub webhook and press "Redeliver":
Jenkins Job does not get triggered by WebHook
In case the web hook has properly been set up, go to the system log (e.g. http://jenkins.mxnet-ci-dev.amazon-ml.com/log/all) and search for something along the following lines:
Received PULL_REQUEST for https://github.com/MXNetEdge/incubator-mxnet from 192.30.252.40 ⇒ http://jenkins.mxnet-ci-dev.amazon-ml.com:8080/github-webhookIf you don't see this message, this means that the we bhook has not been set up properly. consult the previous guide how to continue. This message is a prerequisite for this guide.
To analyze a certain job, go to that job and look for the entry "Repository Events" (e.g. http://jenkins.mxnet-ci-dev.amazon-ml.com/job/test-marco-mxnet-sanity/indexing/events). You will see something along the following lines:
[Tue Nov 20 14:52:10 UTC 2018] Received Pull request #5 opened in repository MXNetEdge/incubator-mxnet CREATED event from 192.30.252.35 ⇒ http://jenkins.mxnet-ci-dev.amazon-ml.com:8080/github-webhook/ with timestamp Tue Nov 20 14:52:05 UTC 2018 14:52:11 Connecting to https://api.github.com using MXNetEdgeBot/****** Examining MXNetEdge/incubator-mxnet Checking branches... Getting remote branches... Checking branch master 16 branches were processed Checking pull-requests... Getting remote pull request #5... Checking pull request #5 ‘ci/jenkins/Jenkinsfile’ not found Does not meet criteria Checking pull request #5 ‘ci/jenkins/Jenkinsfile’ not found Does not meet criteria 2 pull requests were processed Finished examining MXNetEdge/incubator-mxnet [Tue Nov 20 14:52:12 UTC 2018] Pull request #5 opened in repository MXNetEdge/incubator-mxnet CREATED event from 192.30.252.35 ⇒ http://jenkins.mxnet-ci-dev.amazon-ml.com:8080/github-webhook/ with timestamp Tue Nov 20 14:52:05 UTC 2018 processed in 1.7 sec
Here you can see, for example, that the PR did not contain the requested file.
GitHub commit/PR status does not get published
...