GitLab - Garth

Overview

The GitLab integration connects your GitLab Cloud or self-hosted GitLab Server repositories to G360 and collects repository-level engineering data for analytics, reporting, and project tracking. With this integration, you can:

Connect GitLab Cloud or GitLab Server instances
Authenticate using a Personal Access Token (PAT)
Add repositories as data scopes
Associate repositories with projects and scope configurations
Enable repository-level analytics

Prerequisites

Before you configure the integration, make sure you have:

Access to the Engineering Metrics dashboard
A GitLab account with permission to create Personal Access Tokens
Access to the GitLab groups, organizations, and projects you want to integrate
For GitLab Server, version 11 or higher
A GitLab Personal Access Token, created as described in Create a GitLab personal access token

Create a GitLab connection

Open GitLab connections

In Engineering Metrics, go to Integration → Data Integrations Hub. Under Repository Integrations, find GitLab and click Connect (no connection yet) or Manage (existing connection). The GitLab card shows the connection status and available actions.

Start a new connection

On the GitLab Connections page, click New Connection. The Manage Connections: GitLab window opens.

Enter connection details

Field	What to enter
Connection Name	A unique, descriptive name that distinguishes multiple GitLab environments, for example `GitLab Production`, `GitLab Engineering Team`, or `Internal GitLab Server`.
GitLab type	GitLab Cloud, or GitLab Server (v11+) for self-hosted instances running version 11 or higher. See the note below.
Personal Access Token	Your GitLab PAT, for example `glpat-xxxxxxxxxxxx`, entered in the API Token field. The token must have sufficient permissions to access repositories and repository metadata. See Create a GitLab personal access token.
Proxy	Optional. A proxy URL, for example `http://proxy.localhost:8080`, if GitLab can’t be reached directly because of an enterprise firewall, internal networking policy, or restricted outbound access. Leave it empty if no proxy is required.
Custom Rate Limit	Optional. Turn on the toggle to set a fixed API collection rate, for example to prevent API throttling, manage load on a self-hosted server, or control synchronization speed. By default, G360 uses dynamic rate limiting.

Test the connection

Click Test Connection. G360 validates GitLab accessibility, token authentication, and API communication. If validation fails, check for an invalid token, incorrect proxy settings, network restrictions, or GitLab server unavailability, then retry.

Save the connection

Click Save Connection. The connection appears in the Connections panel with the status Connected.

GitLab Cloud: G360 handles the endpoint URL automatically (https://gitlab.com/api/v4/). No URL entry is needed.GitLab Server (v11+): self-hosted environments may require additional network accessibility and authentication validation.

Tokens are stored securely. Revoked, expired, or invalid tokens cause synchronization failures, so make sure the token has not expired.

Create a GitLab personal access token

A PAT authenticates your GitLab account and lets G360 collect repository, project, pipeline, and work item metrics.

Open GitLab and sign in with your account credentials.

Open the Access Tokens page

Click your profile avatar in the upper-right corner, select Edit profile, then select Access Tokens from the left navigation menu. Depending on your GitLab version, this may appear as Personal Access Tokens.

Configure the token

Field	What to enter
Token name	A descriptive name, for example `G360 Integration`.
Description	Optional. A description for the token.
Expiration date	Optional. An expiration date that matches your organization’s security policy.

Select a scope

Select one of the following scopes:

Scope	Description
`api`	Grants the access G360 needs to collect engineering metrics and synchronize project data.
`read_api`	Read-only access, for organizations that prefer a more restrictive permission model.

Create and copy the token

Click Create personal access token, then copy the generated token immediately. Paste it into the API Token field when you create the GitLab connection.

GitLab shows the Personal Access Token only once. Store it securely, because you can’t view it again.

G360 supports the api and read_api scopes. You do not configure separate permissions for projects, repositories, commits, pipelines, organizations, or work items when creating the token. Both scopes cover the access listed in Minimum required permissions.

Minimum required permissions

The token needs the following minimum permissions for G360 to collect organization, repository, project, pipeline, planning, and user-related metrics.

Category	Scope	Required permission	Purpose
Organization	Organizations	`organization`	Access organization-level membership and metadata under GitLab’s top-level Organizations feature. Required for organization-scoped analytics.
Group and Projects	Projects	`project`	Access project metadata and project-level information.
Group and Projects	Groups	`group`	Access group and subgroup information.
Group and Projects	CI/CD	`pipeline`	Access pipeline and CI/CD execution data.
Group and Projects	Repository	`repository`	Access repository metadata.
Group and Projects	Repository	`code`	Access source code and repository contents.
Group and Projects	Repository	`commit`	Access commit history and commit-related data.
Group and Projects	Project Planning	`work_item`	Access work items, including issues and planning data used for engineering metrics.
User	System Access	`user`	Access basic user profile information.
User	Groups	`group`	Access the groups associated with the authenticated user.

GitLab’s Organizations feature is a top-level construct above Groups (Organization → Groups → Projects). It is distinct from the Groups permission listed above. Additional permissions are not required unless your organization has specific integration requirements.

Configure data scopes

A data scope is a GitLab repository that you authorize for synchronization. Only repositories in configured data scopes are collected, synchronized, and reported on.

Open Add Data Scope

Select the GitLab connection and click Add Data Scope. The Add Data Scope window opens.

Select repositories

Search by repository name or browse the list. Each entry shows the Repository Name, Organization, and Last Updated timestamp. Select the checkbox beside each repository to include, then click Add Scopes. G360 adds the selected repositories to the integration scope for analytics and synchronization.

Associate projects and scope configurations

The selected repositories appear in the data scope table, with Data Scope, Project, Scope Config, and Actions columns. Associate projects, scope configurations, and repository mappings so G360 organizes repository data under the correct project.

Manage connections and scopes

On the GitLab Connections page, you can:

View and search all configured connections, and search repository scopes. The left panel lists connection names and the total number of configured connections.
Select an active connection and manage the repository scopes associated with it.
Check the connection status on the GitLab card: Connected or Not Connected.

Synchronization and metrics

After you set up the connection and data scopes, G360 synchronizes repository data from the scoped repositories. Repository insights and engineering metrics become available for analytics, and projects can be mapped to repository scopes.

Troubleshooting

Connection test failed

Possible causes

Invalid PAT
GitLab API not accessible, or GitLab server unavailable
Proxy misconfiguration
Network restrictions

Actions

Verify the token permissions.
Confirm GitLab is accessible.
Recheck the proxy settings.
Retry the connection test.

Repositories not appearing

Possible causes

Insufficient token permissions
Repository access restrictions
Synchronization delay

Actions

Verify repository visibility.
Confirm the PAT scope permissions.
Retry the repository refresh.

Integration shows "Not Connected"

Possible causes

Authentication failure
Expired token
Connectivity issues

Actions

Reauthenticate the connection.
Update the PAT.
Validate network access.

Best practices

Use a dedicated GitLab service account instead of personal credentials. This improves security, simplifies credential rotation, and reduces dependency on individual users.
Use descriptive connection names, for example GitLab Prod, GitLab Internal, or Engineering GitLab EU.
Add only the repositories you need for analytics. This speeds up synchronization, reduces API usage, and improves dashboard performance.
Grant only the minimum permissions required.
Validate tokens regularly and rotate PATs periodically. Expired or revoked tokens interrupt synchronization.
Revoke tokens that are no longer in use or may be compromised.
Store tokens in a password manager or secret management solution. Never share them in source code, emails, or chat applications.

Summary

The GitLab integration connects your GitLab repositories to G360. By configuring a connection, adding repository data scopes, and mapping them to projects and scope configurations, your organization gains repository-level analytics and engineering insights.

​Overview

​Prerequisites

​Create a GitLab connection

​Create a GitLab personal access token

​Minimum required permissions

​Configure data scopes

​Manage connections and scopes

​Synchronization and metrics

​Troubleshooting

​Best practices

​Summary

Overview

Prerequisites

Create a GitLab connection

Create a GitLab personal access token

Minimum required permissions

Configure data scopes

Manage connections and scopes

Synchronization and metrics

Troubleshooting

Best practices

Summary