Breaking the CF-Release Monolith
summary
Project splits cf-release into many smaller releases, each with its own CI pipeline that outputs final artifacts which feed a central release-integration pipeline; teams test each release against blessed versions of the others and run CF acceptance tests before promotion. Manifest generation moves toward a single canonical BOSH manifest using BOSH links and reduced templating (no more spiff), making composition the source of truth. The new flow exposes hidden dependencies, shortens feedback loops, and supports weekly-ish releases while the release integration team currently owns the glue process.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:22History of CFRelease
- 5:33The Core Problem
- 12:16Blessed Versions
- 13:29Advantages
- 15:31Crosscutting
- 16:16Layering
- 18:16Release cadence
- 18:56Compatibility matrix
- 19:46Future manifests
- 20:36Overrides
- 21:36Can I Bump
- 24:26Team Ownership
- 25:06Risk
- 25:56Summary
related talks
08mA Year with CF and BOSH
39mManaged CF-as-a-Service: An Operator's Cookbook
32mIntroducing bosh-workspace: how we deploy all things BOSH
05mRelease management as a catalyst for CI/CD
30mWhat's New in the Cloud Foundry Ecosystem?
25mDeploying Cloud Foundry with BBL, Bosh 2.0 and CF Deployment
38mSIG Release - Deep Dive: Release Engineering Subproject
35mReleasing Ceph - Deep Dive Into Build Infrastructure