Atlas and Peon: Dependency Visualization & Management with Kotlin/JS
summary
Atlas parses Gradle, Carthage and SBT build files from GitHub, generates dependency graphs and emits Graphviz PNGs or a machine graph used downstream; Peon (Hestia) topologically sorts that graph, auto-bumps versions, opens ordered pull requests and can cascade a Kotlin bump into 21 PRs. Both are rewritten from Ruby to Kotlin/JS, integrate with private Maven and Slack, and Hestia’s workflow saves hundreds of developer hours daily by making linear, testable repository updates.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:20Outline
- 3:00Background
- 3:59How We Work
- 6:05Decomposition into Libraries
- 7:38Library Dependency Graph
- 9:38What is Atlas?
- 10:57Simplified Graph
- 14:28Minor Version Changes
- 15:22Topological Sort
- 18:49Major Graph Changes
- 19:07Running Hestia
- 25:02Android
- 25:33Hootsuite VIP Server
- 26:01Health Checks
- 26:21Scala at Hootsuite
- 26:59Atlas Extensibility
- 28:26Hestia Extensibility
- 29:44The Future of Atlas and Hestia
- 30:59Shout outs
