Using GitLab Pipelines
Last updated
Was this helpful?
Last updated
Was this helpful?
You can build your custom Continuous Deployment jobs using GitLab Pipelines and .
To start create a new Bolt schedule and make sure to add the deferred_schedule
configuration. Depending on your intended behavior you can choose to defer to another production job or defer back to the last CD run.
API keys are generate at a workspace level.
To be able to trigger Bolt using the API, you will first need to generate API keys for your workspace. Got to account settings and generate your API keys, make sure to save in your password manager:
API key
API secret
API Endpoint
You will need this later when setting up the secret in GitLab pipelines.
Now you will need to create a new .gitlab-ci.yml
file at the root of your project your dbt™️ repository. Copy the code block below and enter the values required.
Set the corresponding values using your credentials for the variable names:
PARADIME_API_KEY
PARADIME_API_SECRET
PARADIME_API_ENDPOINT
GitLab merged results pipelines is a feature available only on Tier: Premium, Ultimate. Make sure to before proceeding to next step.
Finally you need to add the API key and credentials generated in the in GitLab CI/CD pipelines.