8
2
Whenever my Jenkins gets notified about a new git commit to my repository foo, I get the following log/error response on the triggering client:
Scheduled polling of foo
No git consumers for URI ssh://git@localhost:9777/path/to/foo.git
This failed notification does not commence building. Using the manual "Build Now" commences building successfully.
Setup
- I have the Jenkins instance listening on
localhost:8666
. - I have the SSH daemon listening on
localhost:9777
. - Within Jenkins, I have a git-based Maven project:
- "Maven project name" is foo.
- "Git Repository URL" is
ssh://git@localhost:9777/path/to/foo.git
.
- "Git Repository URL" is
- In that bare repository, I have a hook file
hooks/post-receive
with content:
.
# this is file post-receive
curl http://localhost:8666/git/notifyCommit?url=ssh://git@localhost:9777/path/to/foo.git
This building-on-commit-notification used to work well. I have the feeling that it stopped working well once I moved from standard SSH port 22 to non-standard 9777.
What do I have to do to have a commit notification result in a successful build trigger?
Possibly relevant source code files:
2#3 is more important than it seems. Check that you pushed to the correct branch if your job is not configured to build every branch. At least that’s what had me searching for an error for the better part of two hours. And even though the build job is triggered successfully, I still get the “No git consumers for URI” message when pushing. – Bombe – 2014-10-15T14:09:18.650
I have still some piece missing. My "http://jenkins-url:jenkins-port/job/JOB-NAME/scmPollLog/" says "Changes found", but I still get "No git jobs using repository: URL and branches:" :-(. I even installed Poll SCM plugin.
– pevik – 2015-11-04T16:41:48.280