Tools and Infrastructure for Large Teams

on YouTube ↗45m

" summary

Epic uses Perforce with an automated one‑at‑a‑time merge service called RoboMerge (now shipped in UE 4.24) to surface conflicts by email/Slack and spawn interactive shells so the original author fixes them; a five‑person tools team runs ~50 branches on a ~175–200 machine farm. Builds use an XML, parallel‑first pipeline BuildGraph distributed by a scheduler and a lightweight sandboxing/ cache agent BuildAgent; AutoSDK and UnrealGameSync’s BuildHealth deduplicate errors and automate triage.

AI-written summary · about

" chapters (17)

1. 0:00Intro
2. 0:12Background
3. 2:27Agenda
4. 3:03Code-Centric Branching
5. 4:10Content-Centric Branching
6. 5:02Resolving conflicts
7. 8:35Preventing conflicts ahead of time
8. 9:34Registering other branches
9. 12:13Requirements
10. 15:14BuildGraph
11. 17:27Distributed Builds
12. 22:13Virtualization
13. 25:38Workspace Management
14. 29:21BuildAgent
15. 30:47AutoSDK
16. 35:29Build Failures
17. 38:03Build Health System Goals

" related talks

• 36mImproving Developer Iteration in Unreal Engine 5Mark Lintott · Unreal Fest 2022
• 18mTools 4 Tools 4 ToolsJamie Kyle · ZEIT Day 2018
• 01h 08mChallenges of Managing CoreFX repoKarel Zikmund · NDC London 2020
• 28mEmpowering Teams: Transforming Your...Frank Lesniak, Danny Stutz · PowerShell + DevOps Global Summit 2025
• 47mScaling Your Engineering SystemJonathan Creamer · Connect.Tech 2022
• 41mThe Good, The Bad and the Ugly - Building Distributed Teams at RealmChristian Melchior · Mobile Era 2017
• 45mHow GitHub builds GitHub on GitHubNeha Batra, Martin Woodward, Taysser Gherfal, Ashley Willis · Microsoft Build 2024
• 50mImproving Iteration in Geo-Distributed ScenariosPhil Cousins, Joakim Lindqvist, Grace Yen · Unreal Fest 2022