Welcome to the first DaisyHealth podcast. We recently published a Substack on building real continuous delivery, and used Google’s NotebookLM to turn it into an audio podcast for those who’d rather listen than read. The result speaks for itself—give it a listen and let us know what you think. Thanks for tuning in!
DaisyHealth critiques the common misconception of Continuous Delivery (CD) as simply automating builds, highlighting how true CD involves the ability to safely and frequently deploy features as soon as they are completed, rather than batching them into infrequent releases. They explain that their team achieved this by focusing on process discipline and automating existing tools like Jira, GitHub, and TeamCity, rather than adopting new platforms.
Key aspects of their implementation include automatic linking of code changes to Jira tickets for traceability, requiring all automated tests to pass before deployment, using automated Git release scripts for versioning, and crucially, employing feature flags to control the visibility of new features in production, allowing for testing in live environments and phased rollouts. This shift resulted in significant improvements in cycle time, deployment frequency, and the ability for QA to work more efficiently.
Share this post