Continuous Deployment with BitBucket Pipelines

Build custom Continuous Deployment jobs with BitBucket 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 a BitBucket Pipeline

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

bitbucket-pipelines.yml

image: python:3.11

definitions:
 steps:
   - step: &paradime-continuous-deployment
       name: Paradime Continuous Deployment
       script:
         - export PARADIME_WORKSPACE_UID=$PARADIME_WORKSPACE_UID
         - export PARADIME_API_SECRET=$PARADIME_API_SECRET
         - export PARADIME_API_ENDPOINT=$PARADIME_API_ENDPOINT
         - pip install paradime-io
         # Run the Paradime bolt schedule (by slug) and wait for completion
         - paradime bolt run "flowing-pachy-wyy4fs" --wait
       size: 2x
       max-time: 60

# Run on pushes to main
pipelines:
 branches:
   main:
     - step:
         <<: *paradime-continuous-deployment

Add the variables in BitBucket

Add these as BitBucket repository 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 BitBucket Pipelines

Generate API keys

Generate API keys

Create a BitBucket Pipeline

Add the variables in BitBucket

​Generate API keys

Generate API keys

​Create a BitBucket Pipeline

​Add the variables in BitBucket

Generate API keys

Create a BitBucket Pipeline

Add the variables in BitBucket