[supply] return android rollout percentages #22029
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validci/circleci
builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)Motivation and Context
Resolves this discussion: #19432
Android rollouts can be updated via the supply command but as far as I can tell there is no way to retrieve current rollout information for a given track or release. This makes it difficult to automate a rollout strategy, for example we would like to have a release initially rollout to 10% of users the next day 20% the next day 50% and finally 100%. Since app reviews are unpredictable it is difficult or impossible to do this on a set timeline unless we can fetch the current rollout percentage.
If I missed a way to retrieve this information already please let me know!
Description
Adds a new command
google_play_track_rollout_percentages(track: 'production')
that returns a list of rollout percentages for the given track. Heavily inspired / copied from existing commandsgoogle_play_track_version_codes
andgoogle_play_track_release_names
Testing Steps
I tested this locally: