Skip to main content
Paradime’s CI/CD connects your Git provider to Paradime so changes are validated and deployed as part of your pull-request workflow. A CI/CD run is a Bolt schedule, so it can run any commands (dbt™, Python scripts, or app triggers), not only dbt models.
CI/CD features require a Paradime Bolt subscription.

​
Capabilities

​
Turbo CI

Build and test only your changed models on every pull request, in a temporary schema, before they merge. Works with GitHub (native app), and GitLab, Azure DevOps, and BitBucket (via a pipeline).

​
Continuous Deployment

Run a Bolt schedule when changes are merged. Use GitHub-native CD, or trigger a schedule from an Azure, GitLab, or BitBucket pipeline.

​
Chains

Run several Turbo CI or on-merge schedules in the order you choose, on GitHub. Each step starts only after the step before it passes, so a failure stops the rest of the chain.

​
Lineage Diff Analysis

See the downstream impact of your changes directly in the pull request. The lineage diff report identifies changed columns in your dbt™ models and lists every downstream object affected, including other models and BI-layer nodes.

​
Deferral and state comparison

Both Turbo CI and Continuous Deployment can defer to a previous run so they build only what changed. Set deferred_schedule_slug to the slug of the production schedule to compare against. Paradime reads that schedule’s most recent successful run’s manifest.json (unless you set successful_run_only: false) to determine the new and modified resources. To compare against a whole Bolt environment instead of one schedule, set defer_environment_slug to the environment’s slug. See Defer to an environment. Your commands can then use the state:modified+ selector to build only the changed models and their downstream dependencies:
See Schedule Settings for the schedule-level toggle, and the dbt state comparison documentation.