Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.jitera.ai/llms.txt

Use this file to discover all available pages before exploring further.

GitLab integration enables connecting self-managed GitLab repositories as code sources within Jitera projects. Users authenticate with a Personal Access Token (PAT) through the Jitera UI — no Helm chart configuration is required.

​
Prerequisites

  • A self-managed GitLab instance running version 16.8 or later
  • A GitLab account with admin-level access
  • A Personal Access Token with the api scope
  • Outbound HTTPS (port 443) access from the Kubernetes cluster to the GitLab instance
GitLab.com is not currently supported for self-hosted deployments. Only self-managed GitLab instances can be connected.

​
Creating a Personal Access Token

The steps below are provided as an example. Refer to the GitLab Personal Access Token documentation for the most up-to-date procedure.
  1. Log in to your GitLab instance as an admin user
  2. Go to User Settings > Access Tokens
  3. Create a new token with the following settings:
FieldValue
Token nameA descriptive name (e.g., Jitera Integration)
Expiration dateSet according to your security policy
Scopesapi
  1. Click Create personal access token
  2. Copy the generated token — it will not be shown again
The token must belong to an account with admin access to the repositories you want to connect. The api scope grants full API access, which is required for repository operations.

​
Connecting GitLab in Jitera

No Helm chart configuration is required for GitLab integration. The connection is configured entirely through the Jitera UI — see Code Sources for the connection steps. When prompted, select GitLab, enter your self-managed host URL, and paste the Personal Access Token created above.

​
Troubleshooting

​
Authorization Failed

Symptoms: Error when trying to authorize the GitLab connection Solutions:
  1. Verify the Personal Access Token is valid and has not expired
  2. Confirm the token has the api scope
  3. Ensure the token belongs to an account with access to the target repositories
  4. Check that the GitLab instance hostname is correct and reachable

​
Repository Not Listed

Symptoms: Expected repositories do not appear after authorization Solutions:
  1. Verify the token owner has access to the repository
  2. Check repository visibility settings in GitLab
  3. For group repositories, verify the token owner has at least Maintainer access to the group

​
SSL Certificate Errors

Symptoms: SSL/TLS errors when connecting to self-managed GitLab Solutions:
  1. Ensure the GitLab instance uses a valid SSL certificate
  2. For custom CA certificates, add the CA to the trusted store. Refer to your Kubernetes distribution’s documentation for mounting additional CA certificates into pods.

​
Connection Timeout

Symptoms: Connection times out when trying to reach GitLab Solutions:
  1. Verify outbound HTTPS (port 443) is allowed from the Kubernetes cluster to the GitLab instance
  2. Check network policies and firewall rules
  3. Confirm the GitLab hostname resolves correctly from within the cluster: 
    kubectl exec -it deploy/jitera-automation-rails -n jitera -- nslookup gitlab.yourcompany.com

​
Network Requirements

Ensure outbound HTTPS (port 443) access from the Kubernetes cluster to your GitLab instance. See Network and Firewall → 3rd Party Integrations for the full allow-list, including self-managed GitLab.

GitHub Integration

Configure GitHub integration

Integrations Overview

All available integrations

Requirements

Deployment requirements