Most mobile teams can tell you what their cloud bill is. Few can tell you what a release costs when it is done by hand: the person who remembers the version number, holds the signing key, and knows which tests to run first. That is not a process. It is a dependency on one individual.
What Automation Actually Costs
The usual objection to a build pipeline is cost. The published numbers do not support it. GitHub prices a standard Linux 2-core runner at $0.006 per minute (GitHub), so a ten-minute validation run on every proposed change costs six cents. The same ten minutes on a macOS runner is $0.62, roughly ten times more, which matters because an Android build has no reason to run on a Mac.
The risk in a pipeline is not the per-minute rate. It is the job nobody is watching. GitHub's limits page states that "Each job in a workflow can run for up to 6 hours of execution time" (GitHub). A hung test with no timeout set will use all of it.
Where the Signing Key Lives
The signing key is the asset. If it sits on a laptop, the release schedule belongs to whoever owns the laptop. The standard pattern is to store it as an encrypted secret that is injected only at build time. GitHub documents the constraint plainly: "Secrets are limited to 48 KB in size" (GitHub). The key never enters the code repository, and no single machine is required to ship.
Release to Some, Not All
Automation also changes how much a bad release can cost. The widely used Play upload step accepts a release status of inProgress with a userFraction, described as the "Percentage of users who should get the staged version of the app" (upload-google-play). A defect that reaches one user in twenty is a different business event from one that reaches everyone.
What to Ask Your Team
- Who can ship if one person is out? If the answer is nobody, the release process is a person.
- Does every job have a timeout? The default ceiling is six hours.
- Are builds running on the cheapest runner that works? For Android, that is Linux.
- Does a release go to everyone at once? It does not have to.
-Rocky
#DevOps #ReleaseManagement #CICD #EngineeringDreams #StrategiaX
Originally published on ANDROID-ARCHITECT, the Android engineering blog of Strategia-X, with the full workflow files.