Continuous Integration (CI/CD)

Develop and manage your Holistics project like software, with validation, environments, and pull requests built in.

Advanced users may want to create a CI/CD workflow in Holistics so they can develop and manage their Holistics project in a formal software development manner. This page maps out the main use cases and points you to the right guide for each.

Your current setup

This document assumes you have a setup like the diagram below.

• An ETL setup for your Data Warehouse transformation (dbt)
• A BI layer (Holistics) to build reports and dashboards on top of the data in your Data Warehouse
• The code is hosted by a Git service provider (GitHub/GitLab) integrated with a CI/CD system (GitHub Actions, CircleCI)

Use cases

Holistics supports four main CI/CD use cases, depending on how your team builds and ships changes.

dbt to Holistics validation

When you change dbt models, validate whether the changes break or affect any BI reports, and sync metadata so dbt and BI stay in step.

Read the guide →

Dynamic dev/prod environment

Point models, datasets, and dashboards at your development sources during development, then switch them to production automatically on publish.

Read the guide →

Holistics validation

Detect which dashboards and datasets break when you change a Holistics data model, before the change reaches production.

Read the guide →

PR workflow and auto-deploy

Auto-create a pull request while developing in Holistics, then auto-deploy new code when the PR is merged in GitHub/GitLab.

Read the guide →

Process overview

Here's how these pieces fit together across a typical development-to-production flow.