TeamForge Git integration reference

GERRIT_REPLICATION_MODE
Use this site-options token to set the Git integration server as either 'master' or 'slave' server. In case you do not want replication (standalone mode) or you have only one primary source for repositories, set this token to master. On the other hand, if you have a master Git integration server and you want to replicate (mirror) its repositories on a secondary slave Git integration server, set this token to slave on the slave Git integration server.

GERRIT_REPLICATION_MASTER_EXTERNAL_SYSTEM_ID
If GERRIT_REPLICATION_MODE is set slave, this token specifies external system ID of the 'master' Git integration server.

Mappings between TeamForge and Gerrit
These tables shows how objects and relationships are mapped between TeamForge and Gerrit.

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

Mappings between Gerrit Access Control and TeamForge source code permissions

Gerrit directory structure, connectivity and more
Here's some reference information on Gerrit's scalability and hardware requirements, file/directory structure, database, ports and connectivity.

Gerrit configuration properties
Gerrit provides many configuration options. In addition, CollabNet Gerrit plugins also have configuration options.

Technical differences compared to vanilla Gerrit
Version 16.10 of the TeamForge–Git integration is based on a slightly modified version of Gerrit 2.13.x. Here's how this version is different from vanilla Gerrit.

Illustrations on TeamForge-Gerrit communication
The following illustrations help you understand the communication flow between TeamForge and Gerrit in a single host and distributed environments.

Gerrit performance cheat sheet