Getting VSTS to "Production"
summary
Eight hundred people across about fifty feature teams ship VSTS from a monolithic repo with short‑lived topic branches, a three‑week release branch cadence (and daily deploys for some services), protected PR policies, and hardware requirements for local debugging via virtualization. Builds run 75,000 unit tests and handle roughly 800 pull requests per day onto master, automated commit security scans, feature flags per account/user, and production rollout onto scale units and rings with telemetry at ~980,000 req/min.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:23About Microsoft VSTS
- 0:58Team Structure
- 1:38Hardware Requirements
- 2:21PR Policies
- 2:52Unit Tests
- 3:33Feature Flagging
- 4:03Feature Flagging Example
- 4:22Architecture
- 4:33Scale Units
- 4:43Telemetry
- 5:06Outro
related talks
44m#Devops Journey
33mMoving 75,000 Engineers To DevOps On The Public Cloud
27mUser Feedback at the Speed of DevOps
49mContinuous Delivery for Legacy Code
01h 01mA team's transition to Continuous Delivery
01h 02mEffective DevOps for Organizations
28mMoving to 1ES
53mReal world DevOps with the Microsoft ALM Rangers