Android Basics: Continuous Integration
summary
Concrete takeaways: set up builds that run Gradle, unit tests and Espresso on real devices, run lint/PMD/Checkstyle/FindBugs and Kotlin detector tools, and save artifacts and reports so regressions are traceable. Jenkins is free but many hosted CI vendors add features and cost. Firebase Test Lab is billed by device minute. Mobile-focused services like buddybuild records video replays of Espresso runs and deploys to Play Store and testers, which proves whether automation actually works.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 2:55Socially awkward engineers
- 3:17Charles Dickens
- 4:39Overview
- 5:46Example
- 7:52Mark Zuckerberg
- 8:58Most of us are terrible
- 10:10Henry Ford
- 11:31The Venetian Arsenal
- 12:14Youre Lazy
- 13:18Michael Guerra
- 14:55Continuous Deployment
- 15:51CI Tools
- 19:46Firebase Test Lab
- 21:54Jenkins
- 22:18Jenkins website
- 22:56Jenkins Travis CI
- 23:49Circle CI
- 25:17Matt Harris
- 25:56Buddy Build
- 28:05Buddy Build Dashboard
- 28:21Buddy Build Summary
- 30:27Buck
- 31:13Why Continuous Integration is interesting
- 32:32Joel Spolsky
- 34:27Summary
- 34:48Questions
related talks
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
32mBuilding Quality Android Apps for the Future with Continuous Integration
20mContinuous integration for mobile
26mAndroid CI: 2016 edition
27mGra Fi Te: Leveraging Gradle and Firebase for Android Testing
39mTaming Public Device Clouds for App Testing
53mCI for Android Using Jenkins
39mBuilding, Testing & Deploying Android Apps with Jenkins