On Mon, Jan 13, 2014 at 4:35 PM, Mark Waite <mark.earl.wa...@gmail.com>wrote:
If your git server is allowed to use "curl" to read a URL on your Jenkins > server, then you can use a git commit hook to notify the top level project > on any submission to all of the repos you listed. Each repo would have a > hook to the same URL (the URL for your top level job) so that any time a > change was submitted to any one of the projects, the project will build. > > Refer to Kohsuke Kawaguchi's "Polling Must Die" blog posting for hints on > how to configure it. > > > http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ > > The multiple SCM plugin may also be able to do that, and would probably > allow you to see the commits in the "Recent Changes" portion of the job > definition. However, that will probably be more complicated than adding a > hook to each of your git repositories. > > Mark Waite > > Mark, Thanks for the hint. I have read Kohsuke's blog posting before, and already make extensive use of curl to poke Jenkins to trigger builds. I have this: repo1 -> contains the main repo, with the Makefile that has the "make checkout" target repo2 repo3 repo4 Based on what you have suggested, in the commit hooks for repo2, repo3, and repo4, I will put an invocation of curl that notifies repo1. Thanks! -- Craig -- 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.
