Android CI in the cloud (en)
summary
Compares hosted CI options with a working Android project of 140k lines and measures real outcomes: only CloudBees runs managed Jenkins with plugins and wakes VMs on demand, reducing a 40‑minute build to 5–10 minutes; uses the android sdk manager gradle plugin by jake water to auto‑install SDKs; boots AVDs headless (no GPU or snapshots) under ~80s but cannot reliably start Android 19+ emulators.
AI-written summary · about
chapters (20)
- 0:00Android CI in the cloud
- 1:07Continuous integration for Android
- 2:33Android CI setups today
- 3:59Limitations of Jenkins servers
- 6:26Cloud-based CI solutions
- 7:29Cloud CI solutions compared
- 8:53Limitations in cloud CI tools
- 10:21CloudBees for Android CI
- 11:44Android CI job on CloudBees
- 12:50Updating Android SDK in CI
- 14:37Fixing SDK update issues
- 15:17Performance gains with cloud CI
- 15:38Android emulators in CloudBees
- 16:43Emulator limitations in CloudBees
- 17:23SonarQube in CloudBees
- 18:52Emulator support for old Android
- 19:35Testing lowest Android version
- 20:39Modern Android architectures in CI
- 21:43Emulator testing solutions
- 22:46Key takeaways and call to action
related talks
53mCI for Android Using Jenkins
37mAndroid meets Docker
54mFrom Laptop Builds to Advanced CI
39mBuilding, Testing & Deploying Android Apps with Jenkins
42mConquer Mobile App CI/CD Challenges Using with a Device Cloud
24mLessons in CI_CD from 3500 Android Teams
38mAndroid Basics: Continuous Integration
25mDevOps for Android supercharged with AI