Continuous Delivery
Continuous Delivery is the practice of automating data code changes to a state ready for production deployment, requiring explicit approval for the final production promotion.
Continuous Delivery (CD) automates the entire pipeline up to but not including production deployment. Code passes CI tests, automatically promotes to staging, passes staging tests, and waits for explicit approval before production deployment. CD provides the speed benefits of continuous deployment (automated promotion through early environments) with a safety gate (human approval before production). It enables "deploy on demand": production deployments are always ready but happen when someone approves them.
Continuous Delivery emerged as a compromise between manual deployment (slow, bottlenecked) and continuous deployment (too risky for some organizations). CD provides rapid feedback (changes reach staging in minutes) while maintaining human control (someone must approve production promotion). Different organizations have different risk tolerance: financial institutions often use CD with strict approval gates, while fast-moving startups use full continuous deployment.
Continuous Delivery requires similar infrastructure to CD: CI tests, staging environments, and automation pipelines. The difference is the final gate: a manual approval step before production. This gate can be automatic (after X hours in staging, auto-promote) or manual (person explicitly clicks "deploy"). Organizations often tie approval to business stakeholders: an analyst must approve data changes, a finance manager must approve financial metrics. CD enables rapid iteration while preserving necessary governance.
Key Characteristics
- ▶Automates promotion through all pre-production environments
- ▶Requires explicit approval for production deployment
- ▶Maintains human control over production changes
- ▶Enables rapid promotion through early stages
- ▶Requires strong testing and validation
- ▶Supports multiple deployment strategies
Why It Matters
- ▶Governance: Maintains human approval for production
- ▶Speed: Automated progression through early stages
- ▶Safety: Slower deployments reduce risk
- ▶Control: Organizations choose when to deploy
- ▶Compliance: Approval gates satisfy audit requirements
Example
A metric definition change progresses: developer commits code, CI tests pass automatically, staging tests validate against production-like data and pass automatically, change sits in staging awaiting approval. A finance manager reviews the metric definition change, approves it, and production deployment occurs. The entire pre-approval process took 2 hours; approval timing is up to the business.
Coginiti Perspective
Coginiti's promotion workflow within the Analytics Catalog embodies continuous delivery: code automatically advances from personal workspace to shared (with testing), then to project hub (production) only upon explicit approval. Coginiti Actions enables scheduled job automation with configurable cron schedules and misfire policies, while the version control system tracks all changes for audit compliance. The three-tier workspace structure paired with mandatory code review gates provides the automated pre-production progression and human approval mechanism that defines continuous delivery governance.
Related Concepts
More in Collaboration & DataOps
Analytics Engineering
Analytics engineering is a discipline combining data engineering and analytics that focuses on building maintainable, tested, and documented data transformations and metrics using software engineering practices.
Code Review (SQL)
Code review for SQL involves peer evaluation of SQL code changes to ensure correctness, quality, and adherence to standards before deployment.
Continuous Deployment (CD)
Continuous Deployment is the automated promotion of code changes to production immediately after passing all tests, enabling rapid delivery with minimal manual intervention.
Continuous Integration (CI)
Continuous Integration is the practice of automatically testing and validating data code changes immediately after commit, enabling rapid feedback and early error detection.
Data Collaboration
Data collaboration is the practice of multiple stakeholders working together on shared data work through version control, documentation, review processes, and communication tools.
Data Deployment vs Release
Data deployment is the technical action of moving code to an environment (staging, production), while a release is the business decision to make changes available to users.
See Semantic Intelligence in Action
Coginiti operationalizes business meaning across your entire data estate.