The message "No Git consumers using SCM API plugin for: /D/Repositories/Project" is usually not an indication that notifyCommit was completely ignored.
There are two messages which are reported if a notifyCommit is called and no Jenkins job is polling that URL: $ notify=http://localhost:8080/git/notifyCommit $ bad_url=git://github.com/jenkinsci/git-client-pluginxxxx.git $ curl -s $notify?url=$bad_url Gives jenkins.log output which says: No git jobs using repository: git:// github.com/jenkinsci/git-client-pluginxxxx.git and branches: No Git consumers using SCM API plugin for: git:// github.com/jenkinsci/git-client-pluginxxxx.git There is one message reported if a notifyCommit is called and at least one Jenkins job is polling that URL: $ notify=http://localhost:8080/git/notifyCommit $ good_url=git://github.com/MarkEWaite/bin.git $ curl -s $notify?url=$good_url Gives jenkins.log output which says: Scheduled polling of JENKINS-24368-github-https-auth-fails-private-repo No Git consumers using SCM API plugin for: git:// github.com/MarkEWaite/bin.git The "No Git consumers using SCM API" means that there are no jobs polling SCM which use the GitSCMSource API (the git implementation of the SCM API). In my case, I have at least one job that is polling, without using the SCM API. The URL in your job definition needs to match the URL in your notifyCommit URL. Are they the same (at least in the portion prior to any arguments)? Mark Waite On Fri, Aug 12, 2016 at 3:18 PM John Thornborrow <thornborrow.j...@gmail.com> wrote: > We just have the one windows box that hosts all of our stuff so jenkins > and the git repo are on the same box. No slaves/remote agents. Project > builds fine if we use trigger build API, manually build, or actually poll > git. Literally the only problem we are stuck with is notifyCommit not > recognising the project's git URL because it is a local path and not a > (web) service path. > > Tried changing the config to git bash compatible path > (/D/Repositories/Project) but still the same problem: > > "No Git consumers using SCM API plugin for: /D/Repositories/Project" > > Thanks, > J > > On 12 August 2016 at 22:09, Mark Waite <mark.earl.wa...@gmail.com> wrote: > >> If you're using command line git, you might try /D/Repositories/Project. >> >> That syntax may work on the same machine which hosts the repository. >> That won't work for an agent running on a different machine, or a Jenkins >> server hosted on a different machine. >> >> If you need to use agents which are not the same machine as is hosting >> the repository, you'll need a protocol that can be used across the >> network. If you need to use agents which are not Windows, then you'll need >> a network aware protocol (like http, https, or ssh). >> >> If you host your git repository on Windows, you should plan on exploring >> interesting territory that others do not commonly explore. Most git >> repositories are hosted on Linux and other Unix-like operating systems >> (MacOS, FreeBSD, Solaris, OpenBSD, NetBSD, HP-UX, etc.) much more >> frequently than they are hosted on Windows. Windows Jenkins jobs are >> generally slower than Linux Jenkins jobs, especially for git operations. I >> don't know if that is due to virus scanning overhead, or some other form of >> overhead, but even with git's file system caching enabled, my test jobs >> still take longer on Windows than on comparable Linux machines. >> >> On Fri, Aug 12, 2016 at 1:41 PM John Thornborrow < >> thornborrow.j...@gmail.com> wrote: >> >>> Hi! >>> >>> Build(s) configured with repo: >>> >>> D:/Repositories/Project >>> >>> post-commit hook configured with: >>> >>> curl http://server/git/notifyCommit?url=D:/Repositories/Project >>> >>> Always returns: "No GIT consumers using SCM API plugin for: >>> D:/Repositories/Project" >>> >>> Job definitely has SCM Poll checked. >>> >>> Any clues? I've tried using file:///D:/Repositories/Project and other >>> logical variants (always ensuring both the url=$REPO matches the config >>> value *exactly*) but to no avail. >>> >>> Many thanks, >>> John >>> >>> -- >>> 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. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/d6be236e-b904-461e-8060-c57cd4246b36%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/d6be236e-b904-461e-8060-c57cd4246b36%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/KFXEKNld-cc/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-users+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF%2BXdA%3D6bi_tMEYirwvLa-EQ59%2BxTWUcFLxKknUfYt9Nw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF%2BXdA%3D6bi_tMEYirwvLa-EQ59%2BxTWUcFLxKknUfYt9Nw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . > > >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAPMWfiVtNRQ-%3De6hETpHdRkQMLOGCKH4dmo1JmiKgSZmLggO6Q%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPMWfiVtNRQ-%3De6hETpHdRkQMLOGCKH4dmo1JmiKgSZmLggO6Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHp1jkEbJmMsm3yfFM33MxwFbfbSqvMti6oajCJAy61NQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
