CI for Android Using Jenkins
summary
Jenkins runs a one-compile-then-parallel-test pipeline that triggers on GitHub pull requests, copies built APK artifacts to downstream jobs, and reports pass/fail so merges block on failing checks; plugins actually used include Android emulator plugin, GitHub pull request builder, JUnit reporting and the copy-artifact step. Tests split into unit, component, integration and blackbox shards (espresso hitting real servers), with 1700 unit tests and emulators that boot in ~35–40s; Spoon captures useful screenshots for flaky UI failures and the system works in production.
AI-written summary · about
chapters (19)
- 0:00Intro
- 3:10What is Jenkins
- 8:30Logs
- 12:56Running individual tests
- 16:18Overview
- 16:49Testing Pyramid
- 20:42App Flow
- 22:13Continuous Jobs
- 23:44Trigger
- 24:53Continuous Delivery
- 26:27Server Tests
- 30:07Pipeline View
- 31:04Source Code Management
- 34:32Jenkins Executor
- 34:51Multi Job
- 36:48Matrix Plugin
- 38:39Android Emulator Plugin
- 41:19Android Emulator Pros Cons
- 44:50Mac Mini Setup
related talks
20mContinuous integration for mobile
39mBuilding, Testing & Deploying Android Apps with Jenkins
24mAndroid CI in the cloud (en)
26mAndroid CI: 2016 edition
55mJenkins CI Pipeline using Appium tests for Android and iOS
45mCI Excellence With Test Automation Engineers
32mBuilding Quality Android Apps for the Future with Continuous Integration
36mAndroid like a (reliable) Rock Star - All About Android Continuous Integration
