Skip to main content
November 4, 2026
A GitLab pipeline for a merge request commit, with an external stage that holds the Paradime Lineage Diff and Paradime Turbo CI statuses, both passed
Before this release, Turbo CI on GitLab ran from a .gitlab-ci.yml job on your own GitLab runners, with a Paradime API key in your CI variables. With the GitLab connection, Paradime receives the merge request events itself and runs your Turbo CI schedules. You don’t need a pipeline, a runner, or an API key.
  • Runs on every change. Turbo CI runs when a merge request opens, reopens, gets a new commit, or leaves draft, and only when it changes files in your dbt™ project. Models build into a temporary schema, which Paradime deletes when the merge request merges or closes.
  • Statuses on the merge request. Each Turbo CI schedule posts its own commit status, and Paradime Turbo CI shows the overall result.
  • Chains and the merge queue. Run Turbo CI schedules in order with chains, the same as on GitHub.
  • A summary when it fails. When a run fails, DinoAI posts a summary of the failure as a merge request note. Comment @paradime retry to run the failed step and the steps after it again.
Your current .gitlab-ci.yml pipelines keep working. You can move to the GitLab connection one schedule at a time. See Turbo CI on GitLab. Shipped in Paradime v6.24.0.