Android Meets Docker
6 likes40,134 views
The document discusses the integration of Docker in the Android development workflow, highlighting advantages such as faster build times and resource isolation. It covers performance comparisons between various Android testing methods and addresses challenges such as memory management within Docker. The document also mentions strategies for optimizing Gradle distributions and caching to improve development efficiency.
![Reveal
• Encoding problem
expected:<Hall[]chen> but was:<Hall[ö]chen>
• Hard coded Timezone in test
expected: 2099-12-31T00:00:00.0000+0200
but was : 2099-12-31T00:00:00.0000+0000
• File & Path
File#listFiles() -> File[] (sort order depends on OS)
Machine-dependent Problem](https://image.slidesharecdn.com/ndxlseivrcyh5m6g8bhp-signature-2faa027f6cbb67d7ba80f1af7214eb82cd81bb6ef5ae33d30fee48f5b35c583a-poli-171025040200/85/Android-Meets-Docker-18-320.jpg)
Android Meets Docker
- 3. Pain in the provision ∞ machines ( e.g. mobile CI ) Admin
- 5. Why Docker? Docker Vagrant Resource Isolation Low Extreme Supported OS Linux * Boot / Stop Time Seconds Minutes Size MB GB
- 6. Docker for Android? Infer - A tool to detect bugs in Java and ... code. Run Android SDK update in Docker container AUFS doesn't support hardlink move operations.
- 7. Solution for SDK update Mount SDK volume in container • Minimal • Flexible • Persist • Share
- 8. NFS ✓ In one place ? Performance No concurrent writing
- 9. Benchmark
- 10. Performance Comparison 2 build types, 107 unit tests ( x2 = 214 ), 2 UI tests ./gradlew clean check :demo:connectedAndroidTest On-premises Docker (w/ cached AndroidSDK) 6 mins 48.0 secs Other online CI solutions (w/o optimization) > 10 mins
- 11. Android Devices • ARM emulator • x86 emulator (requires KVM) • USB (needs privileged mode, ⛔ for macOS) • Wifi • Genymotion Cloud
- 12. Performance of 📱 2 UI tests ARM emulator @🐳 2 mins 4.615 secs x86 emulator @🐳 (on Linux Host) 23.497 secs Genymotion 25.335 secs
- 13. Out Of Memory
- 14. Memory Matters JVM is not container aware _JAVA_OPTIONS -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap Exit Code 137 = 128 + 9 = SIGKILL = Killed 1 = SIGHUP = Hangup Comment killed by the kernel OOM killer JVM terminates the program and exits
- 15. Can we get any better? Gradle distributions
- 16. Gradle distributions mirror server • From: gradle/wrapper/gradle-wrapper.properties • To: ~/.gradle/wrapper/dists • SSL certificate - needs to be trusted by Java keystore • /etc/hosts
- 17. And better? Gradle caches • Don’t waste time downloading dependencies • ~/.gradle/caches/
- 18. Reveal • Encoding problem expected:<Hall[]chen> but was:<Hall[ö]chen> • Hard coded Timezone in test expected: 2099-12-31T00:00:00.0000+0200 but was : 2099-12-31T00:00:00.0000+0000 • File & Path File#listFiles() -> File[] (sort order depends on OS) Machine-dependent Problem
- 19. What Else for Mobile • Integration Test • Prod / Test server • unreliable network • complex setup • Docker • out of the box for mobile dev • Something else • Serverless ( Kotlin, Swift ) - reuse 📱 code
- 20. Thank you! ! thyrlian " thyrlian Docker Image: https://github.com/thyrlian/AndroidSDK