Continuous deployement on Android with the publishing API
summary
Explains how to automate APK uploads and store metadata using Google Play’s Publishing API, showing the service account JSON key fields to configure, the Java (and Ruby/Python) client libraries used, and the sample Gradle/Jenkins plugins that usually hide this work. Demonstrates the app edit transactional commit model, use of listings/images/apks/tracks resources, the new reviews API, and staged rollouts with staged rollout userFraction. Includes a working sample project and notes on validate vs commit and thread‑blocking execute calls.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:38Continuous Delivery vs Continuous Deployment
- 5:58Bugs
- 9:32Developer API
- 9:43Publishing API
- 12:48Google Play Console
- 13:23Google Developer Console
- 14:09Service Account Key
- 14:44Private Key
- 15:13Play Store
- 16:13Play Developer Console
- 16:42Animated gifs
- 17:04Microsoft Paint
- 17:35Publisher Library
- 18:08Credentials
- 19:34Instantiate Publisher
- 20:10App edits
- 21:21Validate vs Commit
- 23:12Listing example
- 24:49Resources
- 25:24APK Object
- 28:52Reviews
- 32:05Current state
- 34:54Sample projects
- 35:42Advertising
related talks
38mFrom Development to Production: Tips to Optimise Android App Deployments
41mRelease management: Successful launches and updates on Google Play
38mLevel up your Android build
39mBuilding, Testing & Deploying Android Apps with Jenkins
25mHow We Optimized Our Release Flow Using Google Play Console Release Tracks
57mThe Road to Mobile DevOps for Android
32mBuilding Quality Android Apps for the Future with Continuous Integration
40mAutomate The Small Things