Prerequisites
- An Admin role in Paradime.
- A production Bolt schedule to defer against (Turbo CI uses state comparison to detect changes).
- Your git provider connected to Paradime: the Paradime GitHub App on GitHub, or the GitLab connection on gitlab.com or GitLab Self-Managed. On Azure DevOps or BitBucket, you need admin access to add a pipeline.
Already running Turbo CI with --target ci?
Follow the migration guide to move to a dedicated CI environment and drop the
--target ci flags.Steps
1
Create a dedicated CI environment
Turbo CI runs in its own Bolt environment so CI builds use a separate connection and target from production. In Settings > Environments, create a new environment (for example,
CI), then add a warehouse connection to it with its target name set to ci. See Create and manage environments.2
Add a custom schema macro
So CI runs build into an isolated, temporary schema, add a
generate_schema_name.sql macro to your project’s macros folder. When the target is ci, models build into a schema prefixed paradime_turbo_ci_pr_ (followed by the PR number):3
Create the Turbo CI job
Create a Bolt schedule of type Turbo CI, with:
- Its Environment set to the CI environment you created, so runs use the CI connection and
citarget. - A production schedule to defer to, so state comparison knows what changed.
- Commands that use the
state:modified+selector to build and test only new and changed models, for exampledbt build --select state:modified+. The environment supplies thecitarget, so you do not append--target ci. - A trigger set to run when a pull request is opened.
4
Connect your git provider
Finish by connecting Turbo CI to your provider, so each pull request starts the job and gets the status back:
- GitHub or GitLab: there is nothing to add to your repository. Once the GitHub App or the GitLab connection covers your repository, Paradime starts the Turbo CI job on each pull request or merge request.
- Azure DevOps or BitBucket: add a pipeline that calls the Bolt API when a pull request opens.
GitHub
Native, through the Paradime GitHub App.
GitLab
Native, through the GitLab connection.
Azure DevOps
An Azure Pipeline calls the Bolt API.
BitBucket
A Bitbucket Pipeline calls the Bolt API.
Open a pull request that changes a model. Turbo CI runs, builds the changed models into a
paradime_turbo_ci_pr_<number> schema, and the run status appears on the PR. On GitHub and GitLab, a DinoAI summary of the failure is posted on the pull request or merge request if the run fails. If nothing runs on GitHub or GitLab, check that the GitHub App or the GitLab connection covers your repository.Next steps
Run several Turbo CI checks
Split pull request checks into schedules that run side by side.
Chain Turbo CI checks
Run the checks one after another and stop at the first failure.
Turbo CI reference
The full setup, environment variables, and schema cleanup.
Schedule types and triggers
How the Turbo CI type and PR trigger fit together.