How we migrated the CI / CD of our Android app to GitHub Actions
summary
Migrates a legacy Google Cloud Build pipeline to GitHub Actions, replaces complex Docker images with reusable actions (Gradle action, upload-artifact, Java and checkout actions), and adds App Center deployment via the App Center CLI installed with Node/npm. Initial runs cost ~16 cents per build and take longer than Cloud Build; switching to Buildjet runners cuts runtime to ~8–10 minutes and tuning (manual zipping, timeouts, smaller VM) reduces cost to 6 cents per build, a 10x cost drop while keeping tests, artifacts and Slack notifications.
AI-written summary · about
chapters (14)
- 0:00Introduction and motivation
- 1:09Context and migration decision
- 2:55GitHub Actions core concepts
- 4:19Setting up the workflow steps
- 8:13Handling deployment with App Center
- 9:42Managing secrets securely
- 10:48Workflow run reports and analysis
- 11:08Initial cost and time results
- 12:13Configuring jobs and runners
- 13:18Using Buildjet for faster runs
- 14:42Optimizing artifact uploads
- 15:47Adding timeouts for stability
- 17:15Adjusting runner resources
- 18:22Final results and key takeaways
related talks
29mA brief guide to setting up CI for Android with GitHub Actions
48mBuilding an Android CI Pipeline With GitHub Actions
46mQuality Beyond Testing: Jenkins to GitHub Actions Migration: Optimized Processes & QA
40mAutomating Android Workflows with Github Actions
55mGitHub Actions - CI:CD and more
43mRewriting an Old CI/CD on GitHub Actions for 280 Contributors?
30mPragmatic, scalable, and ergonomic CI/CD using Github Actions and K8s.
31mGetting Started with CI/CD using Github Actions