Intel’s Middle Out Journey to DevOps
summary
Intel replaces quarterly manual QA with an automated pipeline built on Electric Commander (Electric Flow) plus a custom UI, email notifier and dashboard, completing a two‑year rollout that runs ~12,000 tests/day, cuts QA cycle to about 10 minutes, supports hardware reservation and parameterized builds, and scales from ~4 releases/year to 100+ releases/year while keeping headcount flat and surfacing code coverage, memory‑leak and binary‑compatibility metrics automatically.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:43SOC validation
- 3:45Quarterly releases
- 4:39Current cycle time
- 6:30Reasons to automate
- 9:18Parameterization
- 10:06Custom Solution
- 11:28Test Cases
- 12:11Feedback Loop
- 13:08Email Notifier
- 13:54User Interface
- 14:48Dashboard
- 16:27Reservation
- 19:35Benefits
- 21:02Conclusions
- 21:39Biggest challenge
- 23:40Use case
- 24:40Known failures
related talks
26mIntel’s Journey to Large Scale DevOps Transformation
43mThe Road to DevOps
48mDevOps Culture & Practices to Create Flow
30mQA in DevOps: Transformation thru Automation via Jenkins
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
01h 09mScaling up with Embedded Testing
25mDevOps Bringing a New Concept to Software Quality
35mUsing the DevOps Pipeline to Generate Continuous, Valuable Insights