GitLab integrations

Connecting self-managed GitLab to issue trackers, secrets managers, Kubernetes clusters, chat and other CI systems through its documented integrations.

GitLab and Jira integration

Linking self-managed GitLab with Jira Cloud or Data Center: the Jira issues integration versus the development panel, which features each gives, and what project data becomes visible in Jira.

GitLab CI/CD secrets from HashiCorp Vault

Pulling CI/CD secrets from HashiCorp Vault or other external secrets managers with ID tokens, the Premium tier requirement, and Vault roles that limit secrets by project and branch.

Connecting GitLab to Kubernetes clusters with the agent: GitOps with Flux versus CI/CD access, agentk and KAS on self-managed GitLab, supported Kubernetes versions and moving off certificate-based clusters.

GitLab and Mattermost integration

Running Mattermost next to GitLab after the bundled component was removed in GitLab 19: notifications, slash commands and single sign-on between the two.

GitLab and Jenkins integration

Triggering Jenkins pipelines from GitLab and reporting status back to merge requests, used while CI/CD moves to GitLab gradually or where Jenkins jobs must stay.

GitLab and Redmine issue tracker integration

Using Redmine as the external issue tracker for GitLab projects: linking issue references in commits and merge requests, and when to move issues into GitLab instead.

GitLab and Harbor container registry integration

Using Harbor as the container registry for GitLab projects: the group or project-level settings, the six HARBOR_* CI/CD variables pipelines use to push and pull, and how project settings override group defaults.

GitLab CI/CD OIDC authentication to AWS, Azure and Google Cloud

Replacing long-lived cloud keys in CI/CD variables with ID tokens: how jobs exchange a JWT for temporary AWS, Azure or Google Cloud credentials, the aud and sub claims to condition roles on, and why stable project IDs matter after renames.

GitLab webhooks and system hooks for event-driven automation

Choosing between project or group webhooks and instance-wide system hooks, signing payloads with HMAC-SHA256 instead of the plain secret token, and handling the automatic disabling of failing webhooks.

GitLab and Datadog CI Visibility integration

Sending GitLab pipeline and job data to Datadog: the instance, group or project settings, the optional CI Visibility and job log collection, and the per-committer billing to check with Datadog first.

GitLab notifications in Microsoft Teams with Power Automate workflows

Moving GitLab Teams notifications off retired Office 365 connectors to a Power Automate workflow: the template change GitLab documents, the events to enable and limiting pipeline alerts to broken pipelines.

GitLab with YouTrack, Linear, Bugzilla or ClickUp issue trackers

Keeping issues in an external tracker while code lives in GitLab: which trackers GitLab integrates natively, the custom issue tracker option for others, and inheriting the setting from the instance or group.

Managing GitLab integrations at instance and group level

Setting integration defaults once for a self-managed instance: instance and group settings, project inheritance and overrides, and the integration allowlist administrators use to limit which integrations can be enabled.