“Continuous delivery improves both delivery performance and quality, and also helps improve culture and reduce burnout and deployment pain.”
– Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
We, the undersigned, reckon that parin’ down continuous delivery (CD) to its core is required if we wanna improve the flow of delivery and achieve the outcomes above. While our contexts may vary, there are universal practices common in all. By defining ’em, we can:
- Introduce new practitioners in a consistent way
- Discuss engineering practices that make up CD
- Help each other get better at doin’ it
Only by implementin’ core practices do we begin to see the benefits of continuous delivery.
The practices below are the bare minimum, a startin’ point. Continuous improvement of the speed, quality, and safety of the delivery pipeline is the expected outcome. If all y’all do is automate some things then bless your heart, ain’t nothing gettin’ better.
CD is the engineering discipline of deliverin’ all changes in a standard way safely. How you do it depends on what’s bein’ delivered. However, there are things you gotta do in every context to qualify as “Continuous Delivery”
The minimum activities required for CD are:
- Use Continuous Integration
- The application pipeline is the only way to deploy to any environment
- The pipeline decides the releasability of changes. Whatever it says, goes
- Artifacts created by the pipeline always meet the organization’s definition of deployable
- Immutable artifact (no human changes after commit)
- All feature work stops when the pipeline is red
- Production-like test environment
- Rollback on-demand
- Application configuration deploys with artifact
CI is the activity of mighty frequently integratin’ work to the trunk of version control and verifyin’ that the work is, best we can tell, releasable.
The bare minimums for CI are:
- Trunk-based development
- Work integrates into the trunk at least daily
- Y’all automated the testin’ before mergin'
- Work is tested with other work automagically on merge
- All feature work stops when the build halts and catches fire
- New work does not mess up delivered work
Trunk-based development is the branchin’ pattern we need to meet the definition of CI. It prevents lost work, the risk of corruption that comes from conflictin’ changes, and reduces back-and-forth commiseratin’ that makes changes bigger.
The minimum activities required for TBD are:
- Everythin’ integrates into the trunk
- If branches from the trunk are used:
- They start at the trunk
- They end at the trunk
- Like mayflies, they should die within a day
Why’d we build this?
We wrote that down along with some other stuff to help y’all out.
Headin’ Down the Trail
Wanna know where to start? Check out some ideas that’ve worked for us.
Do you want to submit a translation, good practices, suggestions, or talk about what’s worked for you?
Read our contribution guidelines.