Practical Android CI/CD with GitHub Actions and Kotlin script
summary
Pipeline uses GitHub Actions with Kotlin scripts, running on a self-hosted macOS runner for fast Android emulator tests; it runs build, unit, lint and Facebook screenshot tests (instrumentation), posts PR comments, uploads artifacts and automerges when green. A Kotlin kscript generates changelogs via git+Jira CLI by diffing commits since last deployment. APKs upload to Firebase App Distribution, Play internal track receives app bundles, end‑to‑end tests run in Firebase Test Lab, and final production rollout stays manual.
AI-written summary · about
chapters (10)
- 0:00Introduction to CI/CD
- 3:18Why use CI/CD for Android
- 10:08GitHub Actions overview
- 13:45Kotlin script for automation
- 18:21Pull request validation workflow
- 21:41Slack commands for QA builds
- 27:26Generating changelogs with Kotlin
- 32:15Production deployment process
- 35:13Tips for efficient workflows
- 38:47Q&A session
related talks
48mBuilding an Android CI Pipeline With GitHub Actions
29mA brief guide to setting up CI for Android with GitHub Actions
40mAutomating Android Workflows with Github Actions
19mHow we migrated the CI / CD of our Android app to GitHub Actions
40mAutomate All The Things!
27mPractical CI/CD for React Native
42mFocus on What Matters by Automating the Small Things
30mPragmatic, scalable, and ergonomic CI/CD using Github Actions and K8s.