> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Bolt CI/CD for dbt™ pull requests and deploys

> Overview of Paradime's CI/CD suite for dbt™: Turbo CI runs models changed in a pull request, and Lineage Diff surfaces column-level impact for reviewers.

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](/products/bolt/creating-schedules/deploy), so it can run **any commands** (dbt™, Python scripts, or app triggers), not only dbt models.

<Danger>
  CI/CD features require a [Paradime Bolt](https://www.paradime.io/pricing) subscription.
</Danger>

## Capabilities

### [Turbo CI](/products/bolt/ci-cd/turbo-ci/index)

Build and test only your changed models on every pull request, in a temporary schema, before they merge. Works with [GitHub](/products/bolt/ci-cd/turbo-ci/github) (native app), and [GitLab](/products/bolt/ci-cd/turbo-ci/gitlab), [Azure DevOps](/products/bolt/ci-cd/turbo-ci/azure-devops), and [BitBucket](/products/bolt/ci-cd/turbo-ci/bitbucket) (via a pipeline).

### [Continuous Deployment](/products/bolt/ci-cd/continuous-deployment/index)

Run a Bolt schedule when changes are merged. Use GitHub-native CD, or trigger a schedule from an [Azure](/products/bolt/ci-cd/continuous-deployment/azure-devops), [GitLab](/products/bolt/ci-cd/continuous-deployment/gitlab), or [BitBucket](/products/bolt/ci-cd/continuous-deployment/bitbucket) pipeline.

### [Lineage Diff Analysis](/products/bolt/ci-cd/lineage-diff/index)

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. Your commands can then use the `state:modified+` selector to build only the changed models and their downstream dependencies:

```bash theme={"system"}
dbt build --select state:modified+ --target ci
```

See [Schedule Settings](/products/bolt/creating-schedules/schedule-settings#defer-to-a-previous-run) for the schedule-level toggle, and the [dbt state comparison documentation](https://docs.getdbt.com/reference/node-selection/state-comparison-caveats).


## Related topics

- [Turbo CI for dbt™ pull requests](/products/bolt/ci-cd/turbo-ci/index.md)
- [CI/CD Templates](/products/bolt/creating-schedules/templates/ci-cd-templates/index.md)
- [Test Code Changes On Pull Requests](/products/bolt/creating-schedules/templates/ci-cd-templates/test-code-changes-on-pull-requests.md)
- [Deploy Code Changes On Merge](/products/bolt/creating-schedules/templates/ci-cd-templates/deploy-code-changes-on-merge.md)
- [Continuous Deployment with GitHub for dbt™](/products/bolt/ci-cd/continuous-deployment/github.md)