GitLab integration
GitLab data, in your warehouse.
A built-in ingestr connector: add credentials, pick tables, schedule it.
name: raw.projects
type: ingestr
parameters:
source_connection: gitlab
source_table: 'projects'
destination: snowflake
incremental_strategy: merge$ bruin run assets/raw/gitlab.asset.yml
- extract · GitLab projectsincremental
- load · snowflake raw.projectsmerged
- checks · not_null, unique
Loaded and checked. Downstream models can run.
How it connects
Connected in three steps.
DevOps platform
- 01
Add a GitLab connection with its credentials.
- 02
Pick the tables to load and how: replace, append or merge.
- 03
Bruin runs it on your schedule and checks every load.
Tables
5 tables, ready to load.
projectsmerge_requestsissuespipelinesusers
Step-by-step
Pick a destination.
The platform
Part of the Bruin platform.
Data in, ready for everything downstream: the models, the checks, the lineage and the AI layer.
Sources
DatabasesWarehousesApps & APIsFiles & storageStreams & webhooksWeb scrapingMove
Data IngestionEngineering & DevOps
More tools, same category.
Frequently asked
Questions about GitLab.
Does Bruin have a built-in GitLab integration?
Yes. Built-in ingestr source. Runs Bruin pipelines.
Which GitLab tables can Bruin load?
projects, merge_requests, issues, pipelines, users.
Where can GitLab data go?
Snowflake, BigQuery, Databricks, Redshift, ClickHouse, Postgres, DuckDB, MotherDuck, Microsoft Fabric and more, plus files on S3 and GCS.
How fresh is the data?
As fresh as your schedule. Incremental loads append, merge or replace a time window, every few minutes if you like.
Do we need Bruin Cloud?
No. The Bruin CLI and ingestr run locally, in CI or in your own orchestrator. Bruin Cloud adds scheduling, lineage, alerts and the AI data analyst on top.
Ready to connect GitLab?
$100 in credits and 50 AI tasks. No credit card.
A demo walks through your own data.