Industry-Validated Best Practices for Implementing CI/CD
To create this guide, Densify compiled information from experts and businesses in the public cloud and cloud native architectures space who have implemented CI/CD as part of their DevOps strategy. All identified similar challenges which are revealed in the guide.
Ultimately, we identified 8 common phases to successful CI/CD pipelines:
Download the 8 Phases of Continuous Integration & Delivery Guide Now
- The Plan phase often combines practices from Scrum and Agile to enable frequent microincremental releases.
- The Code phase focuses on core development tasks from within IDEs and appropriate sandboxing and frameworks.
- The Build phase rapildy and incrementally merges code commits with some testing and security validation.
- The Test phase focuses on automated verification of enhancements, often incorporating test-driven deployment practices. Testing is sometimes incorporated as part of the Build phase, and generally extends in some way to all phases of the CI/CD process to ensure continuous feedback and improvement.
- The Release phase is centered around repository commits and adequate documentation of the changes.
- The Deploy phase is the actual update to the codebase, with special thought given to issue and error avoidance.
- The Operate phase occurs once the code is made live, and consists of monitoring and orchestration.
- The Monitor & Optimize phase takes place parallel to the Operate phase and consists of data collection, analysis, and feedback to the start of the pipeline and to other phases as needed. In the most sophisticated environments, optimization is automated as continuous optimization (CO), an extension of CI/CD that leverages machine learning to eliminate risks and waste associated with manual infrastructure selection.