Moving Android Project Builds Off the Developer Machine to a Server
summary
How to move Android project builds off developers' machines onto remote servers to reduce local build time. Covers options for organizing remote builds, specific tools for running builds on powerful servers, and practical experience using those tools to build large, multi-module Android apps.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 2:34Speaker background
- 3:39Why build on server
- 6:06Remote build requirements
- 7:52GUI vs command line
- 8:56X-server graphics
- 10:41X2Go remote solution
- 11:49JetBrains tools overview
- 13:13GUI approach pros/cons
- 14:37Command-line builds
- 15:40Project file transfer
- 17:25Build result return
- 18:28Server environment setup
- 19:12Tool installation
- 20:59Frame tool overview
- 21:42Miracle for Android
- 23:53Miracle pros/cons
- 25:41Miracle automation scripts
- 26:47Android Studio plugin
- 29:16Plugin features
- 31:26Plugin server setup
- 32:31Enable/disable remote build
- 33:34Plugin results
- 34:58Plugin limitations
- 36:47Plugin pros/cons
- 38:12Project results
- 39:59GUI vs CLI comparison
- 41:03Team deployment
- 42:06Q&A
related talks
42mStop Building the Project and Start Working
41mDude, Where's My Build? Android CI/CD at Uber
40mScaling Android Apps
52mmulti-module Android application
35mRelease Android apps globally with no headache and minimum stress
01h 00mAndroid builds
40mCase Study- How Android Platform @ Reddit learned to stop worrying and embrace DevX
45mMake or brake… using Gradle.