Automating Android Workflows with Github Actions
summary
Explains how GitHub Actions runs Android CI using YAML workflows that map trigger events to jobs, each job running on a runner machine; demonstrates a real Android CI YAML (Signal repo) with one 20‑minute Linux job, how a build matrix spawns many parallel jobs (OS × JDK) and the needs keyword chains jobs, shows a screenshot‑testing pipeline that syncs device folders (Nexus 4, Pixel) to avoid plugin limits, and warns that emulators need MacOS runners (costly) and caching requires choosing between actions/setup‑java, actions/cache or Gradle’s caching action.
AI-written summary · about
chapters (12)
- 0:00Introduction and setup
- 1:30GitHub Actions five core concepts
- 5:50Runner machines and jobs explained
- 8:44Real-world workflow example
- 13:45Custom actions and marketplace
- 16:14Scaling pipelines horizontally
- 18:45Build matrix for parallel jobs
- 22:26Custom topologies with needs
- 26:40Case study screenshot testing
- 33:21Android tips for GitHub Actions
- 35:06Caching in CI pipelines
- 38:20Final remarks and resources
related talks
48mBuilding an Android CI Pipeline With GitHub Actions
45mLights, Camera, GitHub Actions!
47mLights, Camera, GitHub Actions!
48mCICD with Github Actions
43mCI/CD with Github Actions
29mA brief guide to setting up CI for Android with GitHub Actions
59mIntroduction to GitHub Actions
56mLights, Camera, GitHub Actions!