GitLab has evolved a lot since I first asked about support with Gitolite. I personally like the approve feature which can force a code review before merge.
Our Gitolite administrator have comprised a list of features that we rely on with Gitolite. From what I can see GitLab does not support all of them. Must have features: * Manage users individually and in groups * Define groups of repositories and allow group administration of repositories (give or limit access to many repositories for certain users), without having to add for each repository. * Per-branch user access (none|read|write|create|delete|force-update) * Tag access that can be controlled independently from branch and commit access (for instance, a user get access to push tags, but not commits) * Namespace control for tags (a user gets access to push tags within a given namespace) * General namespace control (gives personal namespace with full access within namespace for users and groups) * Everything above must also allow for management individually per repository. * Allow for command line management of git this setup. GUI is fine, but should not rely solely on it. Gitolite has functionality that supports the above: * Define repositories * Define users * Defines groups of users * Auto defined user groups, for instance @all * Define groups of repositories (include wildcard repositories systems/..*) * Auto defined groups of repositories, like @all * Define groups based on existing groups (but for instance minus/plus one or several users) * Define access on all levels (repositories/users/groups/branches/tags/namespace) * Access levels: none (deny), read, write, write+ (push -f), create, delete mandag 2. mars 2015 22.31.22 UTC+1 skrev sytse følgende: > > We don't recommend using Gitolite with GitLab, you'll have to make the > switch. > > Best regards, > Sytse Sijbrandij > CEO GitLab B.V. > > > On Tue, Feb 24, 2015 at 6:08 AM, Sverre Moe <sverr...@gmail.com > <javascript:>> wrote: > > Well, for one we have used Gitolite for years. It is a proven solution > and > > it works very well. We want to continue using it at least for the > > foreseeable future. > > Secondly, our Gitolite is under administration from a different entity > in > > our organization. We want to use GitLab for users to collaborate with > code > > reviews and merge requests. > > > > Gitorious would not work with Gitolite. > > Atlassian Stash did have a Mirror Hook, but didn't work well. > > So GitLab is our last chance to offer a Web UI for some of our users who > are > > not comfortable performing code reviews and merge requests from the > command > > line. > > > > tirsdag 24. februar 2015 04.43.29 UTC+1 skrev Dmitriy Zaporozhets > følgende: > >> > >> Hey, > >> > >> Are there any reasons why you dont want to use GitLab without Gitolite? > >> > >> Best regards, > >> Dmitriy Zaporozhets > >> CTO GitLab B.V. > >> > >> On Mon, Feb 23, 2015 at 7:07 AM, Sverre Moe <sverr...@gmail.com> > wrote: > >>> > >>> Using a clone mirror from Gitolite in GitLab this way doesn't work as > I > >>> hoped. > >>> GitLab does not get the changes that has been pushed to Gitolite after > >>> the cloning. > >>> Merge request performed in GitLab is not pushed over to Gitolite. > >>> > >>> Gitolite v3 has an async push to slaves feature. Perhaps this could be > >>> used to update the mirror repository in GitLab. > >>> > >>> Have anyone successfully been using GitLab 7 against Gitolite? > >>> > >>> fredag 20. februar 2015 12.15.55 UTC+1 skrev Sverre Moe følgende: > >>>> > >>>> I created a project in GitLab, then performed a manual git clone > >>>> --mirror from the repository in Gitolite and removed the GitLab > repository. > >>>> Restarted GitLab and the repository seems to be fine, but I haven't > tried to > >>>> see if it will update when there has been pushed to the Gitolite > repository. > >>>> > >>>> Still manually creating the mirror repository for each project is a > >>>> daunting task. > >>> > >>> -- > >>> 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. > >>> To view this discussion on the web visit > >>> > https://groups.google.com/d/msgid/gitlabhq/add0dfb7-a938-47d0-a286-03b50864d703%40googlegroups.com. > > > >>> > >>> 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+u...@googlegroups.com <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/gitlabhq/eb0e0259-b418-4c54-a426-8c167fc73dec%40googlegroups.com. > > > > > > 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/88228afb-1bd4-453f-be94-635548c10127%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
