Dogfooding Developer Productivity: The Development Process at JetBrains
summary
JetBrains runs a single monorepo: a ~20 GB git folder with 1M+ files and about 10M Java lines, ~400 active developers and 1,000+ CI agents. Builds use JPS and a patched JetBrains Runtime; CI is TeamCity with ~300k distributed tests that form a one‑hour aggregator. Developers use Space, Toolbox Enterprise and a safe push plugin that runs the aggregator before merge. Shared server‑built indexes (built in ~40 minutes) and JPS caches speed local setup; static analysis via Codana keeps zero‑tolerance issues at ~36.
AI-written summary · about
chapters (20)
- 0:00Start
- 5:46Git Repository Hosting: Space
- 7:54Git Repository Branches
- 12:09Environment Setup
- 13:42Toolbox Enterprise
- 14:50Project Setup
- 18:10Shared Indexes
- 21:41JPS Caches
- 22:53IntelliJ Development Pulse
- 23:50CI Server: TeamCity
- 24:43Tests
- 29:39Cherry-Pick Robot
- 30:53Release Build
- 31:45Code Reviews
- 33:48Issue Tracking: YouTrack
- 36:36Exception Analyzer
- 39:43Static Code Analysis
- 42:20Zero Tolerance Inspections
- 43:15JetBrains Products
- 44:26Takeaways
related talks
07mA quick word about JetBrains now and later
28mHow We Use TeamCity to Build TeamCity at JetBrains
20mContinuous Workflow
46mDeveloper Productivity Engineering at CERN
39mMobile Developer Productivity Panel
06h 30mJetBrains Plugin Developer Conf 2025
20mContinuous Workflow
01h 00mWhat We Mean When We Talk About Developer Productivity