Access rights in Gerrit 2.12.x

The Git integration maps Gerrit access rights to TeamForge Role Based Access Control (RBAC) permissions.

How to view/access the TeamForgeGerritMappings.xml file?

In earlier versions (pre-8.1.x) of the Git integration, mappings were established using the gerritforge.mappings properties file. For more information, see Mappings between TeamForge and Gerrit (archives).

The current mappings file TeamForgeGerritMappings.xml is located in the refs/meta/config branch of TF-Projects project . The following table shows how TeamForge RBAC permissions are now mapped to Gerrit access rights by default.

  1. Log on to TeamForge as a Site Administrator.
  2. Select My Workspace > More > Git <hostname>.
    Note: hostname refers to the server where your Git integration is hosted.
  3. Select Projects > List.
  4. Select TF-Projects from the list of projects.
  5. Select the Branches tab.
  6. Click Browse against the refs/meta/config branch name.
The TeamForgeGerritMappings.xml file can be found here.
Code review policy TeamForge permission cluster Gerrit access right
Default SCM None -
SCM View Only Read
SCM Commit/View

Read
Push
Create Reference
Push Annotated Tag (refs/tags/*)
Push Signed Tag (refs/tags/*)

SCM Delete/View

Read
Push (forcePush)
Create Reference
Forge Author Identity
Forge Committer Identity
Push Annotated Tag (refs/tags/*)
Push Signed Tag (refs/tags/*)

SCM Admin

Read
Push (forcePush)
Create Reference
Forge Author Identity
Forge Committer Identity
Forge Server Identity
Owner
Abandon
Push Annotated Tag (refs/tags/*)
Push Signed Tag (refs/tags/*)

Optional Review SCM None -
SCM View Only

Read
View Drafts
Publish Drafts
Code Review  -1,1
Push (refs/for/refs/*)
Rebase(refs/for/refs/*)            

SCM Commit/View

Read
View Drafts
Publish Drafts
Code Review  -2,2
Verify -1,1
Submit
Push
Create Reference
Rebase (refs/for/refs/*)
Push Annotated  Tag(refs/tags/*)
Push Signed Tag (refs/tags/*)

SCM Delete/View

Read
View Drafts
Publish Drafts
Code Review  -2,2
Verify  -1,1
Submit
Push (forcePush)
Create Reference
Rebase (refs/for/refs/*)
Create References
Push Signed Tag (refs/tags/*)
Push Annotated Tag (refs/tags/*)
Push Merges(refs/for/refs/*)
Forge Author Identity
Forge Committer Identity

SCM Admin

Read
View Drafts
Publish Drafts
Delete Drafts
Code Review  -2,2
Verify  -1,1
Submit
Push (forcePush)
Create Reference
Owner
Abandon
Rebase (refs/for/refs/*)
Create References
Push Signed Tag (refs/tags/*)
Push Annotated Tag (refs/tags/*)
Push Merges(refs/for/refs/*)
Forge Author Identity
Forge Committer Identity
Forge Server Identity

Mandatory Review SCM None -
SCM View Only

Read
View Drafts
Publish Drafts
Code Review  -2,2
Push (refs/for/refs/*)
Rebase (refs/for/refs/*)

SCM Commit/View

Read
View Drafts
Publish Drafts
Code Review  -2,2
Verify -1,1
Submit
Push(refs/for/refs/*)
Rebase (refs/for/refs/*)

SCM Delete/View

Read
View Drafts
Publish Drafts
Code Review  -2,2
Verify -1,1
Submit
Push(refs/for/refs/*)
Rebase (refs/for/refs/*)

SCM Admin

Read
View Drafts
Publish Drafts
Delete Drafts
Code Review  -2,2
Verify  -1,1
Submit
Push (forcePush)
Create Reference
Owner
Abandon
Rebase (refs/for/refs/*)
Push Annotated  Tag(refs/tags/*)
Push Signed Tag (refs/tags/*)
Create References
Push Merges(refs/for/refs/*)
Forge Author Identity
Forge Committer Identity
Forge Server Identity

.

To make changes to the mappings, modify the TeamForgeGerritMappings.xml file in the refs/meta/config branch of TF-Projects project on the server where your Git integration is hosted. For instance, if you want to add a user-defined category to your repository, first you need to add the user-defined category to the TeamForgeGerritMappings.xml file. For instructions, see Create a User-defined Repository Category .

Note: Make sure that the resulting XML structure complies with this schema: https://forge.collab.net/gerrit/static/TeamForgeGerritMappings-8.0.0.xsd
.