LogoLogo
  • Datafold
  • Introduction
    • Data Diff
      • Continuous Integration
      • Manual Data Diff
      • Diff Results
    • Column-level lineage
      • Usage, popularity, & impact per table or column
    • Alerting
  • ⏱️Quickstart Guide
  • Getting Started
    • Data Warehouses
      • Snowflake
      • BigQuery
      • Redshift
      • Postgres
      • Databricks
    • Configuration
      • Indexing
      • Filtering
      • Profiling
      • Lineage
    • On-prem Deployment
      • AWS
      • GCP
    • SSO
      • Okta
      • Google OAuth
      • SAML
  • Integrations
    • Continuous Integration
      • Source Control with Git
        • GitHub
          • On-prem Github
        • GitLab
      • dbt Cloud
      • dbt Core / datafold-sdk
        • GitHub example
        • GitLab example
      • dbt Configurations
      • datafold-sdk
    • Alert Integrations
      • Slack integration
        • Slack Alerts
        • On-prem Slack Integration
      • Alerting webhooks
    • Data Apps
      • Mode
      • Hightouch
  • Developer
    • Datafold API
      • Alerting
      • GraphQL Metadata API
      • Data Diff
      • Error handling
    • Security
      • GDPR
      • Network Security
Powered by GitBook
On this page

Was this helpful?

  1. Integrations
  2. Continuous Integration
  3. Source Control with Git

GitLab

This guide will take you through the GitLab integration.

PreviousOn-prem GithubNextdbt Cloud

Last updated 2 years ago

Was this helpful?

Setting up the GitLab integrations requires Admin privileges. Confirm that you have the correct permissions before continuing.

This guide will take you through the required steps to set up Datafold with GitLab. Let's start by adding a new Git config.

The integration name is a reference to the repository.

Datafold requires the Maintainer role.

After saving, it is always a good idea to hit the Test button to check if everything is set up correctly:

After this, make sure to set up a CI under the CI settings.

As the token we both support and personal token. Project access tokens are preferred since they will stay active if the person leaves the Gitlab organization:

For the personal access token; you can fetch the access token from . For the integration the api permissions are sufficient.

Let's use our example repository in GitLab. As the name suggests, this is a simple example setup using dbt with a Snowflake backend.

project access token
your profile page in GitLab
datafold/dbt-snowflake