[ 
https://issues.jenkins-ci.org/browse/JENKINS-13000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162067#comment-162067
 ] 

tfnico commented on JENKINS-13000:
----------------------------------

We ran smack into the same problem yesterday. 

To make matters a bit more desperate, reverting to normal polling leads to 
changes being detected on every poll, so the build is running over and over 
again.
                
> Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin 
> (0.2) are not detected by the remote-trigger hook functionality
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13000
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13000
>             Project: Jenkins
>          Issue Type: Bug
>          Components: git, multiple-scms
>    Affects Versions: current
>         Environment: Jenkins v1.449, Windows7
>            Reporter: Joerg Schwaerzler
>            Assignee: Nicolas De Loof
>              Labels: git
>
> Just tried to do remote-triggering of some jobs to see whether we can make 
> use of post-receive hooks in our git repositories to trigger our build jobs.
> However, jenkins did only recognize jobs where git plugin was 'directly' used 
> without using the multiple SCMs plugin.
> -----
> Any jobs using git plugin within a multiple scms configuration are not found:
> Using "curl '<jenkins url>/git/notifyCommit?url=<repository url>'" we just 
> get (for repositories which are only used within multiple SCMs plugin):
> No git jobs using repository: <repository url>
> -----
> For repositories which are used as well with the stand-alone git plugin we 
> get:
> "Scheduled polling of <repository name>"
> However any job where <repository name> is used in multiple SCMs config is 
> missing here as well.
> Hope it's not too complicated to fix this issue...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to