Continuous Delivery, or the magic button for on‑demand releases
summary
Describes implementing a one-click Continuous Delivery pipeline for a complex distributed product (2GIS Reference API) so a manager can trigger a full release on demand. Covers the workflow and specific tools used: Jenkins for builds, Rundeck for release administration, Yandex.Tank for load testing, and Chef for server configuration.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:15What is Continuous Delivery
- 5:14Release problems and limits
- 10:41Automated testing
- 14:41Infrastructure and deployment
- 18:47Load testing
- 20:15Release process transparency
- 21:24On-demand releases
- 22:53Holistic change approach
- 26:26Time and resources for rebuild
- 27:55DevOps and future plans
- 28:15Test coverage
- 30:03Testers and developers roles
- 31:07Database schema changes
- 32:52Ensuring backward compatibility
- 34:14Q&A
- 36:22Test data preparation
- 37:26Release and config prep
related talks
33mContinuous Delivery - What does good really look like?
30mModern Continuous Delivery
24mWhy, What, and How of Continuous Delivery
42mCONTINUOUS DELIVERY FOR RUBYISTS
55mThe Rationale for Continuous Delivery
32mContinuous Delivery as a Service
45mContinuous Delivery in a World of Constant Change
28mMinimum Viable Continuous Delivery
