CI/CD, Signing & Release
BUILD & TOOLING › Delivery
Automating Android builds, signing keys, and staged Play Store releases.
Release engineering separates engineers who can ship from those who only write code. Interviewers probe whether you understand Play App Signing's two-key model, how to recover from a lost upload key, how staged rollouts and Play tracks de-risk launches, and how Fastlane or GitHub Actions automate the whole pipeline. Expect questions on AAB vs APK, keystore secret handling in CI, and rollback strategy.
What this covers
- Play App Signing: upload key vs app signing key, and why the split exists
- Recovering a lost or compromised upload key vs losing the app signing key
- AAB-only delivery, Play tracks (internal/closed/open/production) and staged rollouts
- Securely injecting keystore and service-account secrets into CI runners
- Fastlane lanes, the supply action, and Gradle build automation
- GitHub Actions / Bitrise pipelines: caching, signing, and store upload steps
Study this topic
- CI/CD, Signing & Release explained: the guided lesson
- 14 practice quiz questions
- 9 revision flashcards
- CI/CD, Signing & Release interview questions and answers