~/talk

Continuous Delivery, or the magic button for on‑demand releases

TalkinRussianat HighLoad++ 2014 · 2014-10-31..11-01· [devops-and-delivery, engineering-leadership]
links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 1:15What is Continuous Delivery
  3. 5:14Release problems and limits
  4. 10:41Automated testing
  5. 14:41Infrastructure and deployment
  6. 18:47Load testing
  7. 20:15Release process transparency
  8. 21:24On-demand releases
  9. 22:53Holistic change approach
  10. 26:26Time and resources for rebuild
  11. 27:55DevOps and future plans
  12. 28:15Test coverage
  13. 30:03Testers and developers roles
  14. 31:07Database schema changes
  15. 32:52Ensuring backward compatibility
  16. 34:14Q&A
  17. 36:22Test data preparation
  18. 37:26Release and config prep
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.