DOES14 - Reena Mathew and Dave Mangot - Salesforce
summary
Salesforce reports growth to 2 billion transactions a day and drives DevOps by embedding quality early: design reviews, tabletop and game‑day destructive testing, and treating Puppet changes as standard to push patches in hours. Engineering teams build tooling—an open source Puppet test harness called roster and a Vagrant‑based dev environment Puppet in a Box—and a CI pipeline that cuts failover from ~12 hours to ~2 then ~35 minutes, aiming for 5.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:11Safe Harbor
- 3:45We Want a DevOps Transformation!
- 7:17Quality Engineering: Definition
- 9:15Testing isn't the only way to guarantee Quality
- 12:04How to Bring Developers In
- 15:04Infrastructure Test Automation
- 16:24Infrastructure Test Environments
- 16:59What Ops Hears
- 19:46Destructive Testing Metrics Destructive testing is a normal part of service deployment
- 20:51What Security Hears
- 22:26QE Collaboration with Security
- 23:45Issue Remediation
- 25:22Quality is Everyone's Responsibility
- 25:49Quality in a DevOps Transformation
- 26:56Takeaways
- 27:38Your Experience
related talks
28mDevOps in the Enterprise: A Transformation Journey
26mService Ownership: DevOps for Salesforce
52mDevops @Scale
33mFrom 0 to DevOps in 80 days
37mDevOps for the Rubyist Soul
22mA Healthier Software Development Life Cycle with DevOps
40mKeynote 'How to explain DevOps to your mom and how it works at Facebook, PayPal and others!'
30mColumbia Sportswear Experience Report