Opening Keynote: Testing in the age of DevOps
summary
Claims that matter: DevOps is coding the policies into pipelines and success is measured by four metrics — lead time to change, mean time to recovery, change failure rate and release frequency — not buzzwords. Demonstrations: ephemeral environments created from infrastructure-as-code (Chef Puppet Ansible), build binaries once, stop-the-line pipelines that run unit acceptance and performance tests, and pipelines-of-pipelines for dependent projects. Surprises: only ~10% report successful adoptions; tools (Jenkins etc) come last; politics and missing policy kill otherwise working automation.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:29Roys background
- 4:11Outline
- 6:25Definition
- 9:18Core value
- 10:02Flow
- 10:43Lead Time to Change
- 13:01Mean Time to Recovery
- 15:12Change Failure Rate
- 16:15Release Frequency
- 17:35Agile
- 21:21Continuous Delivery
- 26:21Pipelines
- 28:58Infrastructure
- 30:37Tools
- 33:18Adoption challenges
- 38:09DevOps battles
- 39:54Adoption phase
- 40:15The elephant analogy
- 40:37Stop the pain
- 41:00Pay attention
- 42:00Recommended books
related talks
45mOpening Keynote: The Enterprise DevOps Mind Trap
01h 19mThursday Keynote
47mHow Testing is Evolving in DevOps
15mTransforming Testing: The Power of TestOps
23mDay 1 Welcome Keynote - Simplifying Software Delivery
34mThe Road More Traveled: Putting Transformation Back on the Rails
54mEffective DevOps for Organizations
34mDevOps Transformation from the C-Level point of view