# Continuous Integration (CI/CD)

> Learn how to create a CI/CD workflow in Holistics so that they can develop and manage Holistics project in a formal software development manner

<Hero
  title="Continuous Integration (CI/CD)"
  subtitle="Develop and manage your Holistics project like software, with validation, environments, and pull requests built in."
  image="https://cdn.holistics.io/docs/v4/ci-cd/ci-cd-overview-setup.png"
  imageAlt="Continuous Integration in Holistics" />

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.

<Columns>

- 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)

</Columns>

## Use cases

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

<CardGrid cols={2}>
  <Card title="dbt to Holistics validation" href="/docs/continuous-integration/automatic-dbt-integration" cta="Read the guide">
    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.
  </Card>
  <Card title="Dynamic dev/prod environment" href="/docs/continuous-integration/dynamic-dev-prod-environment" cta="Read the guide">
    Point models, datasets, and dashboards at your development sources during development, then switch them to production automatically on publish.
  </Card>
  <Card title="Holistics validation" href="/docs/continuous-integration/validation-api" cta="Read the guide">
    Detect which dashboards and datasets break when you change a Holistics data model, before the change reaches production.
  </Card>
  <Card title="PR workflow and auto-deploy" href="/docs/continuous-integration/pr-workflow-auto-deploy" cta="Read the guide">
    Auto-create a pull request while developing in Holistics, then auto-deploy new code when the PR is merged in GitHub/GitLab.
  </Card>
</CardGrid>

## Process overview

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