gitlab team 和 gitlab group 有什么区别? [英] What are the differences between gitlab team and gitlab group?

查看:33
本文介绍了gitlab team 和 gitlab group 有什么区别?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用 Gitlab 5.0 来管理我的 git 存储库,在 Gitlab 之前我从未使用过 github.

当我创建一个组时,我在/home/git/repositories 中看到一个具有该组名的新目录.但是对于团队,没有这样的事情.另外,通过组,我可以为组创建一个项目,并且分配(对于该组的用户)是自动完成的.

我看不出 groupteam 之间的任何其他差异,我想了解这一点.

提前谢谢你,抱歉英语不好(我是法国人),

解决方案

GitLab 6.0 (August 2013, 22d)

参见提交3bc4845:

功能:将团队替换为群组成员

<块引用>

我们在 6.0 中引入了组成员身份,以替代团队.
以前的组和团队组合让很多人感到困惑.
而当团队成员发生变化时,这不会反映在项目权限中.

在 GitLab 6.0 中,您将能够将成员添加到具有每个成员权限级别的组中.
这些组成员将有权访问该组中的项目.
对组成员的任何更改都会立即反映在项目权限中.
您甚至可以为一个群组拥有多个所有者,从而大大简化管理.

<小时><块引用>

那么为什么 GitLab 7 中仍然存在对 Teams 的引用?例如按团队过滤"

作为用户,您是组的第一个成员,并且具有与项目相关联的角色(报告者"、开发者"...)(这使您成为成员该项目的团队"的一部分).
没有角色,意思是不是项目团队的成员".
请参阅 db/migrate/20140914145549_migrate_to_new_members_model.rb.

<小时>

GitLab 5.x 的答案(2013 年 8 月 22 日之前)

  • Group 用于对项目进行分组,类似于文件夹(git 存储库)
  • 团队用于对资源(人员)进行分组

这些概念已经在 GitLab 4.2.

这允许您以更方便的方式管理授权,在一次操作中授予一组项目的权限,和/或授予他们团队引用的一组人的权限.

GitLab 5.x 不再使用 Gitolite,但在 5.0 之前,团队和小组都来自 Gitolite,及其 gitolite.conf 配置文件.
这是声明和关联团队和组以授予权限访问的地方.
即使没有 gitolite,这个想法仍然存在:通过团队(人)和组(项目)之间的关联来管理授权.

I'm using Gitlab 5.0 to manage my git repositories and I've never used github before Gitlab.

When I create a group, I see a new directory with this group name in /home/git/repositories. But with team, no such thing is done. Also, with group, I can create a project for the group and the assignments (for users of this group) is done automatically.

I can't see any other differences between group and team and I would like to understand that.

Thank you in advance and sorry for the bad English (I'm french),

解决方案

GitLab 6.0 (August 2013, 22d)

See commit 3bc4845:

Feature: Replace teams with group membership

We introduce group membership in 6.0 as a replacement for teams.
The old combination of groups and teams was confusing for a lot of people.
And when the members of a team where changed, this wasn't reflected in the project permissions.

In GitLab 6.0 you will be able to add members to a group with a permission level for each member.
These group members will have access to the projects in that group.
Any changes to group members will immediately be reflected in the project permissions.
You can even have multiple owners for a group, greatly simplifying administration.


Why do references to Teams still exist in GitLab 7 then? e.g. "Filter by Team"

As a user, you are a first a member of a group, and have roles ('Reporter', 'Developer', ...) associated to a project (which makes you a member of that project, part of the "team" for that project).
No role, means "not a member of the team for a project".
See db/migrate/20140914145549_migrate_to_new_members_model.rb.


Answer for GitLab 5.x (before August 2013, 22d)

  • Group is for grouping projects, similar to a folder (git repositories)
  • Team is for grouping resources (people)

Those notions have been refined in GitLab 4.2.

That allows you to manage authorization in a more convenient way, given permissions to a group of projects in one operation, and/or given permission to a group of people, referenced by their team.

GitLab 5.x no longer used Gitolite, but before 5.0, teams and groups are coming from Gitolite, and its gitolite.conf configuration file.
This is where team and groups were declared and associated in order to grant permission access.
Even without gitolite, the idea persists: managing the authorization through association between teams (of people) and groups (of projects).

这篇关于gitlab team 和 gitlab group 有什么区别?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆