Skip to content

Add CI/CD best practices page - #76

Open
fmercadop wants to merge 13 commits into
mainfrom
docs/ci-cd-pipelines
Open

fmercadop wants to merge 13 commits into
mainfrom
docs/ci-cd-pipelines

Conversation

@fmercadop

Copy link
Copy Markdown
Contributor

Adds best-practices/ci-cd, an overview of CI/CD for dbt and Airflow in Datacoves:

  • Building blocks: PR databases, Slim CI, governance and Airflow checks, branch rules, QA with production data, blue/green deploys, versioning and full refresh.
  • Two common flows (feature to main, and feature to release to main), with diagrams and a comparison table to help choose between them.
  • Adds the page to the Best Practices navbar dropdown.

Also fixes how-tos/dataops/trigger-cicd-workflow: path filters only stop empty commits from triggering push workflows. On pull_request workflows, an empty commit still triggers them if the PR changes matching files.

Depends on: datacoves/balboa infra/ci-cd-docs. This page links to docs/ci_cd_pipelines.md in Balboa, which doesn't exist on Balboa's main until that PR is merged. Merge both together.

fmercadop and others added 12 commits November 5, 2026 10:27
Add a CI/CD section under How-tos > DataOps describing the numbered
pipeline stages (10, 15, 20, 30), branch validation, the database
lifecycle, Azure DevOps equivalents and variants, and how to customize
branch prefixes, cleanup thresholds, triggers and CI images.
Replace the text diagram in the CI/CD overview with a branch flow image
and add a database lifecycle image, both with descriptive alt text.
Fix inaccuracies found by checking the pages against the pipeline code:
path-filtered stages skip validation, full-refresh label behavior,
staging database left after a failed deploy, shared QA database,
production database lifecycle, CI image contents, and DAG test list.
Move the detailed stage-by-stage CI/CD guides out of How-tos. The
details now live in the Balboa repository; docs.datacoves.com keeps a
single overview under Best Practices that describes the building blocks
and two common flows (feature to main, and feature to release to main).
…fecycle diagram

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…w claims

- trigger-cicd-workflow: path filters only block empty commits on push
  events; on pull_request they are evaluated against the whole PR diff
- CI/CD overview: the empty build catches errors quickly rather than "in
  seconds", and only Azure DevOps is named as another implementation
@fmercadop
fmercadop requested a review from noel November 12, 2026 19:00
@fmercadop fmercadop self-assigned this Nov 12, 2026
@noel

noel commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

@fmercadop can you make the links open new tabs

@fmercadop

Copy link
Copy Markdown
Contributor Author

@fmercadop can you make the links open new tabs

External links already open in a new tab; internal doc links stay in the same tab, which is the standard Docusaurus behavior

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants