Part 4: How Mozilla publishes APKs onto Google Play Store, in a reasonably secure and automated way
The Release Engineering team fully-automated the publication of Firefox for Android in version 53.0. Let’s see what was already there and how things have changed since version 53.0.
This blog post is a part of a serial. Checkout the other posts:
- How did the project start?
- Presentation of the solution
- 5 things I would have loved knowing about Google Play
- What’s next? Want to contribute? & Special thanks [Here]
What’s next? Want to contribute?
The initial publication was the first big step of the project. The next big one will be to expand the release workflow to simplify what percentage of the user base is getting the latest update.
If you want to contribute, there are also a few open bugs. You might also want to take look at MozApkPublisher and pushapkscript to see how we added our checks.
Finally, if you have some stories on how you use Google Play you would like to share, questions or comments about our tools, please leave a comment.
Special thanks
A lot of people were involved in a way or another in this project. By alphabetical order:
- Rail Aliiev, for the help spawning nightly tasks against the correct events and more hints
- Chris AtLee, for guiding me during the entire project and always pointing me in the right direction
- Chris Cooper, for organizing the Taskcluster migration work week, which allowed to put the last bits for Firefox 53.0
- Julien Cristau, for giving feedback from Release Management’s point of view at almost every step we made
- Guillaume Destuynder, for reviewing the security risks
- Ben Hearsum, for reading and testing out the documentation in place
- Liz Henry, for helping with Google Play permissions
- Sylvestre Ledru, for the initial solution and the overall administration of Google Play
- Francesco Lodolo, for detecting and helping diagnose locales-related bugs
- Jordan Lund, for the help in the 52 release duty cycle, while the taskgraph was being finished up in 53
- Ritu Kothari, for initiating the new rollout process
- Amy Rich, for watching my back with Puppet
- Aki Sasaki, for helping me with scriptworker and reviewing so many of my patches across several components
- Mihai Tabara, for wiring the last parts of the Taskcluster graph together
- Justin Woods, for the tips and tricks of Taskcluster’s taskgraph
- Anybody involved in the Android Taskcluster migration, and who might not be in this list
- The reviewers of these articles
- And anyone I missed above
Comments
You can read and leave comments on this Github issue.