> For the complete documentation index, see [llms.txt](https://docs.logilica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logilica.com/integration/connecting-tools/gitlab-pipelines.md).

# GitLab Pipelines

The GitLab Pipelines connector imports your CI/CD pipelines into Logilica so build performance and reliability feed into the [Build dashboard](/metrics-and-reports/build.md), and — once deployment detection is configured — the [DORA metrics](/configuration/dora-configuration.md).

## Authentication

GitLab pipeline data is imported through your existing GitLab connection — there is no separate connector to configure. Once GitLab is connected, Logilica imports pipeline data for each project automatically. See [Connecting Tools](/integration/connecting-tools.md) for how to set up the GitLab connection.

## What's Imported

For each project, Logilica imports finished pipelines and the work beneath them:

* **Pipelines** — identified by their branch reference and trigger source, with a link to the pipeline on GitLab
* **Timestamps** — created, started, and finished times
* **Build outcome** — whether the pipeline succeeded, failed, or was cancelled
* **Triggering user** — the user that ran the pipeline
* **Commit and branch** — the commit and branch the pipeline ran against
* **Merge request associations** — where a pipeline ran against a merge request reference, the associated merge request is linked
* **Stages and jobs** — every job in the pipeline, grouped by its stage

## How Logilica Maps the Data

Build outcomes are normalised so that success, failure, and cancelled results are consistent across every CI/CD platform Logilica supports.

{% hint style="info" %}
**Only finished pipelines are imported.** Logilica requests pipelines that have completed, so runs that are still in progress are left out until they finish and are picked up on a later scan.
{% endhint %}

## Good to Know

* **Kept in sync automatically.** After the initial import, Logilica refreshes this connection on a regular schedule — you don't need to re-trigger imports.
* **First import covers the last 6 months.** The initial scan imports pipelines updated within the last 6 months. Importing older history requires a configuration change by Logilica — contact support.
* **Release detection flags deployments.** Logilica runs [release detection](/configuration/release-detection.md) over imported builds, flagging the pipelines that represent deployments so they can power your DORA metrics.
* **Up to 1000 pipelines per project.** Logilica imports up to the most recent 1000 finished pipelines per project at onboarding. Future pipelines are added to the stored history as they complete.
* **It feeds Build and DORA.** Imported pipelines power the [Build dashboard](/metrics-and-reports/build.md) (build frequency, reliability, speed, and recovery time) and, once [Release Detection](/configuration/release-detection.md) is configured, the [DORA metrics](/configuration/dora-configuration.md).
* **Push your own build data.** If you run builds that this connector doesn't cover, you can send them via the [Build Data Import API](/advanced/import/build-data.md).