If you use the GitHub Webhook method of triggering jobs, the job will be told to 'poll' the repository if it uses the repository that received commits. The job itself can restrict what parts of the repository will actually cause a build to occur, and if the changes in the repository don't affect those parts, no build will happen.
The Jenkins master will still check the repository after each commit to see if the changes are relevant, but builds will only happen if the specified branch(es) were modified. ----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: May 2 2013 12:11:05 We use GitHub and want to be able to trigger builds on Jenkins when a commit is made to a particular branch. Our Jenkins currently only has the git plugin which I believe allows for the pulling from our GitHub repo via ssh public key authorization. I think the GitHub built-in web hook which has our secret token URL as its value and executes for every commit regardless of branch, sends post data with the branch that was committed to via the trigger URL?secret_token. Is there some way to filter this post data before executing the build, and only trigger when the data is for the desired branch, e.g. dev? I am wondering if using polling might be better? Is it possible to poll and only build for changes to a particular branch? Would parameterized builds be useful. Thanks for any help. Bill -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
