Android like a (reliable) Rock Star - All About Android Continuous Integration
summary
Practical roadmap for Android CI that names tools and outcomes: run a build on every commit, run tests, lint and code-style checks, save artifacts, and deploy to testers or the Play Store automatically. Jenkins dominates but needs heavy maintenance; Travis, CircleCI, GitLab CI, TeamCity and Bamboo are viable hosted/self-hosted options. BuddyBuild records video replays, logs and call stacks for UI tests, Firebase Test Lab plugs into CI for device/cloud testing, and Kotlin users can add detekt for static analysis. A mail‑order Delta robot brute‑forced a six‑digit PIN (1,000,000 combos) and succeeded after two full cycles.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 5:01Why continuous integration matters
- 10:59History of continuous production
- 14:16Defining CI and CD
- 16:45Static code analysis tools
- 20:13Survey of CI/CD tools
- 27:41Drama in CI/CD and solutions
- 33:39Joel Spolsky's 17-year-old blog post
- 34:22Kotlin in CI/CD and cost discussion
- 35:48Q&A
related talks
38mAndroid Basics: Continuous Integration
32mBuilding Quality Android Apps for the Future with Continuous Integration
20mContinuous integration for mobile
26mAndroid CI: 2016 edition
31mDude, Where's My Build? Android CI/CD
34mPractical tips for succeeding with CI/CD for Android
41mHow Are Other Teams Doing It? Lessons in CI/CD from 3500 Android Teams
57mThe Road to Mobile DevOps for Android