From Chaos to Consistency: Managing Build and Release for 25+ Android Repos with Github Actions
summary
Migrates 25+ Android repos from ad-hoc Jenkins pipelines to a central CI/CD repo using reusable workflows on GitHub Actions, builds and publishes AARs to GitHub Packages, and automatically assembles the shell app and uploads test builds to Firebase App Distribution. Results: developer effort drops from about six to two hours per sprint across ~22 repos, uses the 50,000 free GitHub minutes, and surfaces limits like noninherited env vars and a 20-workflow nesting cap.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker intro
- 1:15Current architecture overview
- 3:04Previous CI/CD challenges
- 5:55Entering reusable workflows
- 7:41Defining reusable workflows
- 9:28Calling reusable workflows
- 11:35Workflow design and structure
- 13:00Library build and test steps
- 15:29Publishing libraries to GitHub Packages
- 19:25Integrating libraries into shell app
- 21:59Building and distributing shell app
- 23:43Alternative distribution platforms
- 25:08Monitoring workflows in GitHub
- 26:35Dependency management with Dependabot
- 27:41Benefits and results observed
- 30:35Limitations and cost metrics
- 32:43Q&A and closing remarks
related talks
40mAutomating Android Workflows with Github Actions
29mA brief guide to setting up CI for Android with GitHub Actions
48mBuilding an Android CI Pipeline With GitHub Actions
36mPutting an End to “Isn’t this the Same Root Cause as That Project Six Months Ago? Why Didn’t You Prevent It?” — Reusable Workflows …
45mLights, Camera, GitHub Actions!
45mA Call to (GitHub) Actions!
48mCICD with Github Actions
18mDeveloper Workflow Automation with GitHub Actions (CI/CD)