Hmm, either I'm misunderstanding the warning in that configuration file or I'm not 100% clear.
* The symlink itself is not the Gitlab repos_path. * Gitlab's repos_path is a regular folder that contains regular bare repositories. * The symlinks I create are placed in Gerrits repositories path. Gerrit finds them without issues. It is just that Gitlab does not seem to become aware of a merge made within Gerrit. On Tuesday, 14 October 2014 16:00:31 UTC+2, sytse wrote: > > FYI We explicitly warn against making the repo path a symlink > https://gitlab.com/gitlab-org/gitlab-ce/blob/1d432e96bc44ad2f7f67dc4a551d34083f51f281/config/gitlab.yml.example#L236 > > since it has caused a lot of problems in the past. > > Best regards, > Sytse Sijbrandij > CEO GitLab B.V. > > On Mon, Oct 13, 2014 at 8:13 PM, Jonas Hellström <jbh...@gmail.com > <javascript:>> wrote: > >> I've been dabbling with both Gerrit and Gitlab for a very brief period >> and I've come to like them both in their own special ways. >> I'm also collaborating with a few other people who have varying >> experience with both Gitlab and Gerrit, which is why I'm trying to please >> both parties. >> >> I've been successful at setting up Gerrit 2.8 and Gitlab 7.3.2 and they >> seem to be working nicely. >> What I've done in order to satisfy that both Gerrit and Gitlab share the >> same codebase is to point a symlink from Gitlab to Gerrit's repo_home >> folder. This is working out ok, Gerrit sees the repositories. It's also >> possible to clone the repositories from either end and work with them. >> Gitlab shows the commit history of whatever merge is done by Gerrit. >> >> What doesn't work as well as I'd like is that the Dashboard never >> reflects any of the Gerrit-merges. I'm trying to figure out if there's a >> way to add a hook or something else to the merge flow, to trigger Gitlab to >> become aware of the change and make it show up. >> >> This is where I'd like to turn to you all. This setup is not ideal, >> because you would normally not use more than one code review tool, but you >> can see this as an experiment that I'd like to see if it's possible to >> follow through on. >> >> If anyone has a tips on how it would be possible for Gitlab to become >> aware of a Gerrit merge (submit) into a Git repository shared by both >> Gitlab and Gerrit, please share. I'm all ears. :) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "GitLab" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gitlabhq+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/8303ead5-37bb-421f-a3d7-aafec9058d89%40googlegroups.com >> >> <https://groups.google.com/d/msgid/gitlabhq/8303ead5-37bb-421f-a3d7-aafec9058d89%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 the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/351d97ba-5695-462b-ab8e-175a50ec83ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
