How We Use TeamCity to Build TeamCity at JetBrains
summary
JetBrains runs a single TeamCity installation that builds itself and every product 24/7: 1500 build agents, ~6000 projects, 40,000 build configurations and ~300,000 builds per day. Core uses trunk‑based commits (20–40 commits/day) with a nightly BuildServer upgrade driven by a review build that runs 20,000+ tests and several dozen system tests. Frontend uses feature branches with an auto‑merge robot. Production releases come from a merge into a buildserver branch that performs a coordinated merge across 50 repositories; hotfixes are cherry‑picked and deployed the same night.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:27Dogfooding
- 2:26JetBrains BuildServer stats
- 3:20Our setup
- 4:49TeamCity Core workflow
- 6:23Nightly review build
- 8:30Frontend workflow
- 11:05BuildServer duty
- 13:05Merge to `buildserver` branch
- 15:03BuildServer upgrade
- 18:10Secondary server upgrade
- 19:15Cherry picks
- 20:02Summary
- 21:01Q&A
related talks
20mContinuous Workflow
46mDogfooding Developer Productivity: The Development Process at JetBrains
45mContinuous Workflow (Team Tools)
45mContinuous Workflows (Team Tools)
44mContinuous Integration Pipeline Configuration
28mUsing CI to Test the Frontend: the TeamCity Example
06mGetting VSTS to "Production"
20mContinuous Workflow