Dave Green commented on Bug JENKINS-14019

Hi Andreas,

I've encountered this issue as well, but have been able to work round it.

My environment: Windows 2008 R2, Jenkins 1.475, Jenkins Multiple SCMs plugin 0.2, Git plugin 1.1.21, Git 1.7.4.msysgit.0

Workaround: I've been able to work around this issue by creating a separate job monitoring a single Git Repository (I'm only interested in changes in one, but you could set up a trigger job for each repository you are monitoring) and using this job to trigger my multi-SCM job. Obviously I set the polling on the multi-SCM job to be a very large interval or disable it (see below).

Note that this workaround isn't ideal due to (1) additional jobs need to be created, and (2) More space is needed for an additional copy of the Repository being monitored. In the fullness of time I intend to set a very long polling interval and use Kohsuke Kawaguchi's instructions at http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ to get the triggers being "pushed" from Git instead of "pulled" from Jenkins. I believe that this should negate the need for the parent job.

Hope that helps,

Dave.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to