Repository navigation
Conversation
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
Contributor
|
@fmercadop can you make the links open new tabs |
Contributor
Author
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
best-practices/ci-cd, an overview of CI/CD for dbt and Airflow in Datacoves:Also fixes
how-tos/dataops/trigger-cicd-workflow: path filters only stop empty commits from triggeringpushworkflows. Onpull_requestworkflows, an empty commit still triggers them if the PR changes matching files.Depends on: datacoves/balboa
infra/ci-cd-docs. This page links todocs/ci_cd_pipelines.mdin Balboa, which doesn't exist on Balboa'smainuntil that PR is merged. Merge both together.