A brief guide to setting up CI for Android with GitHub Actions
summary
A migration from Google Cloud Build to GitHub Actions recreates build, test, deploy and notify steps using the Gradle GitHub Action, artifact uploads, App Center API/CLI and GitHub Secrets. The concrete changes include switching runners (cutting cost from €0.64 to ~€0.06 per build), using external runners to reduce build time to ~8 minutes, adding timeouts, caching and a custom zip step, publishing test artifacts and pushing APKs to App Center.
AI-written summary · about
chapters (15)
- 0:00CI migration for Android
- 1:54Google Cloud Build CI
- 3:40GitHub Actions basics
- 8:18Running tests and reports
- 10:01Deploying to App Center
- 11:44GitHub Actions secrets
- 13:09Execution reports analysis
- 14:12Cost and performance analysis
- 15:56Optimizing with third-party runners
- 18:01Optimization results
- 19:26Improving test reports
- 20:29Handling timeouts and stability
- 21:33CPU resource optimization
- 22:13Conclusion
- 23:17Q&A
related talks
19mHow we migrated the CI / CD of our Android app to GitHub Actions
48mBuilding an Android CI Pipeline With GitHub Actions
40mAutomating Android Workflows with Github Actions
44mCI/CD with GitHub Actions
48mCICD with Github Actions
55mGitHub Actions - CI:CD and more
01h 01mGetting Started with GitHub Actions
56mCI/CD and beyond with GitHub Actions