Continuous integration for mobile
summary
Starts with Travis CI then moves to self‑hosted Jenkins because control over devices and plugins matters; a templated Jenkins pipeline generation creates per‑branch build, test and distribution jobs automatically. Tests use Robolectric, Espresso and Appium (uploader spells apium) with physical devices, emulators and cloud farms (Testdroid/TestObject/BrowserStack). CI enforces SonarQube code‑quality gates and coverage metrics, uploads artifacts to Crashlytics and HockeyApp, and pushes nightly beta builds to Google Play with Cloud Test Lab monkey runs for automated stability checks.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:50What is Continuous Integration
- 4:10Jenkins
- 5:50Build pipelines
- 7:00Quality gates
- 10:10Unit testing
- 12:00Acceptance tests
- 13:45Integration tests
- 15:30Distribution
- 18:45Outro
related talks
53mCI for Android Using Jenkins
38mAndroid Basics: Continuous Integration
14mMobile CI at Etsy
42mConquer Mobile App CI/CD Challenges Using with a Device Cloud
45mCI Excellence With Test Automation Engineers
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
32mBuilding Quality Android Apps for the Future with Continuous Integration
55mJenkins CI Pipeline using Appium tests for Android and iOS
