Continuous Deployment

Continuous Deployment (CD) runs a Bolt schedule as soon as changes are merged, so your production environment always reflects the latest approved changes. The schedule can run any commands (dbt™, Python scripts, or app triggers), not only dbt models. Bolt integrates with your version control and CI/CD platforms to run the deployment.

​

Deployment options

​

Set up the CD Bolt schedule

For pipeline-based CD (Azure, GitLab, or BitBucket), first create the Bolt schedule your pipeline will trigger. GitHub-native CD does not need this, see GitHub Native.

1. In the Bolt UI, create a new schedule or edit an existing one.
2. Turn on Defer to a previous run so the job builds only what changed, comparing against a previous run’s state.
3. Give the schedule a descriptive name.
4. Choose the schedule to defer to (the same schedule or another).
5. Set the comparison method (Last run or Last successful run).
6. Enter the dbt™ commands to run, for example:
   dbt run --select state:modified
   
7. Choose the Git branch to deploy from (for example, main).
8. Set the trigger to On Merge, so the schedule deploys when changes are merged.
9. Deploy the schedule, and note its slug for the pipeline.