Menu
My Jenkins Continuous Integration Server is on running on a Ubuntu host, configured as follows:
Polling SCM works. This is important to say because I want you to know my other jenkins related configuration is working well except this post build trigger nonsense.
I want to configure Jenkins so that when changes are pushed to a development branch in a private github repository this will then trigger a build that incorporates the most recent changes.
The repo is under my personal github account as owner. Let's call this owner
I am including another github.com account as collaborator. Let's call this collaborator
The reason I am doing this is because in case I am no longer involved in the project, somebody else can carry on with the maintenance.
The SSH keys for the jenkins user in ubuntu are stored under collaborator
I have consulted the following links:
http://nepalonrails.tumblr.com/post/14217655627/set-up-jenkins-ci-on-ubuntu-for-painless-rails3-app-ci
https://issues.jenkins-ci.org/browse/JENKINS-10391
https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin
http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
https://wiki.jenkins-ci.org/display/JENKINS/Logging
http://blog.cloudbees.com/2012/01/better-integration-between-jenkins-and.html
None of it is not working. Some look a bit dated or even contradictory.
I have added github.com to knownhosts for jenkins ubuntu user. I have added the github webhook.
I have tried manual and auto github webhook setup in jenkins.
Nothing works.
I need a step by step guide on how to achieve this without polling github.
726
In review, the steps to configure a Jenkins GitHub webhook trigger is: Create a Jenkins build job that uses a GitHub URL. Click the GitHub hook trigger for GITScm polling checkbox on the build job. Create and copy a Jenkins API token for the Jenkins user who will run the build job.
Follow the steps as mentioned below to trigger a Jenkins job automatically based on GitHub's webhook configurations: Step 1: Go to the Configuration page of the respective job and under the build trigger section, check the "GitHub hook trigger for GITScm polling" checkbox and click on the Save button.
I had a similar problem, and after looking at the main Jenkins System Log I saw the following:
Feb 15, 2013 8:35:44 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /github-webhook/. Returning 403.
The solution is to switch off the CSRF protection - Manage Jenkins > Configure System > Prevent Cross Site Request Forgery exploits. The checkbox is just at the bottom of the first configuration section. After that it all seemed to work happily.
106
Create a logger with trace level logging for the com.cloudbees.jenkins category under your /log url (Manage Jenkins-> System logs).
Verify that there is a Webhook URL entry under the Service Hooks section of your repository administration screen.
Click test hook and you should see some log activity under your newly created logger.
Finally, check the GitHub Polling log action on the build which you have configured to be triggered by GitHub pushes.
A common mistake is testing commit hooks like this without having a change present.
The hook is only used to prompt a poll and won't perform a build unless changes are detected.
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
