Continuous Deployment with Azure Pipelines

Build custom Continuous Deployment jobs with Azure Pipelines and the Bolt API. First set up the CD Bolt schedule and note its slug, then trigger it from your pipeline on merge.

Generate API keys

To trigger Bolt from your pipeline, generate a Paradime API key with the Bolt schedules admin capability. Generate an Account API key (a prdm_cmp_... Bearer token) and save the token, your workspace token, and the API endpoint; you will add them as CI/CD variables in the next step.

Generate API keys

Create an Azure Pipeline

Create an azure-pipelines.yml file in your dbt™ repository and enter the values required.

azure-pipelines.yml

# Run when changes are pushed to main
trigger:
 - main

variables:
 # Slug of the Paradime schedule to run
 - name: PARADIME_SCHEDULE_SLUG
   value: "flowing-pachy-wyy4fs"

steps:
 - task: UsePythonVersion@0
   inputs:
     versionSpec: "3.11"
     addToPath: true
   displayName: Use Python 3.11

 - script: |
     pip install paradime-io

     # $(VARIABLE) references Azure Pipeline variables
     export PARADIME_API_ENDPOINT=$(PARADIME_API_ENDPOINT)
     export PARADIME_WORKSPACE_UID=$(PARADIME_WORKSPACE_UID)
     export PARADIME_API_SECRET=$(PARADIME_API_SECRET)

     paradime bolt run "$(PARADIME_SCHEDULE_SLUG)" --wait
   displayName: "Run Paradime CD"

Add the variables in Azure Pipelines

Add these as Azure Pipeline variables:

PARADIME_API_SECRET — your account API key (prdm_cmp_...)
PARADIME_WORKSPACE_UID — your workspace token
PARADIME_API_ENDPOINT

Schedule Anatomy

Deploy Schedules

Managing Schedules

CI/CD

Continuous Deployment with Azure Pipelines

Generate API keys

Generate API keys

Create an Azure Pipeline

Add the variables in Azure Pipelines

​Generate API keys

Generate API keys

​Create an Azure Pipeline

​Add the variables in Azure Pipelines

Generate API keys

Create an Azure Pipeline

Add the variables in Azure Pipelines