Service hooks - jenkins
Created by: dzaporozhets
Activity
Created by: luxifer
@sdiaz do you actually link your jenkins and gitlab through gitolite? how? and what your jenkins do on your gitlab? Thx
By Administrator on 2012-10-01T11:58:45 (imported from GitLab)
Created by: minioak
You just need to add
curl -s http://jenkins-server/notifyCommit?url=/${GL_REPO}.gitto the
/home/git/share/gitolite/hooks/common/post-receivefile. Is probably worthwhile being able to set it up on a per repository basis though.By Administrator on 2012-10-08T09:32:32 (imported from GitLab)
Created by: sodabrew
Does this tell Jenkins to run any builds associated with that repository?
On Mon, Oct 8, 2012 at 2:32 AM, John Mitchell notifications@github.comwrote:
You just need to add
curl -s http://jenkins-server/notifyCommit?url=/${GL_REPO}.git
to the /home/git/share/gitolite/hooks/common/post-receive file. Is probably worthwhile being able to set it up on a per repository basis though.
— Reply to this email directly or view it on GitHubhttps://github.com/gitlabhq/gitlabhq/issues/1432#issuecomment-9220498.
By Administrator on 2012-10-08T15:50:41 (imported from GitLab)
Created by: minioak
I believe it simply tells Jenkins to trigger a poll on an already configured Git repository.
See https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository
By Administrator on 2012-10-08T15:54:01 (imported from GitLab)
Created by: sodabrew
That would be a more complicated!
On Oct 8, 2012, at 8:58 AM, Florent VIEL notifications@github.com wrote:
I already have that, i expect a feature like in github. I want jenkins to build merge request in gitlab and display the result in these ones. like travis bot, or like github pull request plugins
— Reply to this email directly or view it on GitHubhttps://github.com/gitlabhq/gitlabhq/issues/1432#issuecomment-9230474.
By Administrator on 2012-10-08T16:41:00 (imported from GitLab)
Created by: sodabrew
@minioak According to the Jenkins doc: "We require the polling configuration on the job so that we only trigger jobs that are supposed to be kicked from changes in the source tree." Hmm, ok. We don't currently use repo polling at my site, but if the poll time could be set high enough to be irrelevant (like, poll once every 3 million years) that would be a fair workaround :)
By Administrator on 2012-10-09T14:51:46 (imported from GitLab)
Created by: elvanja
Hi guys! Not really sure whether it's the right place (being a closed issue), but @Riyad pointed me in this direction. In issue #1840 (closed) I wrote about Gitlab Web Hook plugin for Jenkins that does pretty much all mentioned here, except "building merge requests" (and probably what Gitlab-CI does, but I haven't tried it so can't really tell). Feel free to take a look. As always, there is room for improvement, and for new features, if needed.
By Administrator on 2012-12-07T22:24:57 (imported from GitLab)
Created by: drf
+1, this and #739 (closed) are the only things left for Gitlab to take over my previous git infrastructure
By Administrator on 2013-01-22T14:10:37 (imported from GitLab)
Created by: dosire
Moved to http://feedback.gitlab.com/forums/176466-general/suggestions/3788056-service-hook-for-jenkins-ci
By Administrator on 2013-03-27T09:01:05 (imported from GitLab)
