Skip to content

ci(android): adopt staged Play rollout #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dkhalife merged 1 commit into from
Aug 3, 2026
Merged

ci(android): adopt staged Play rollout #372

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .azuredevops/android-build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,13 +48,9 @@ extends:
- name: aab
path: android/app/build/outputs/bundle/release
artifact: aab
# No approval gate — continuous deploy to the internal track only. Release-
# intent stages auto-skip on PR builds (stages/release.yml in the shared
# template), so this never runs during PR validation.
- stage: release_canary
templateContext:
intent: release
environment: canary
jobs:
Comment thread
dkhalife marked this conversation as resolved.
- job: play_store
templateContext:
Expand All @@ -63,6 +59,5 @@ extends:
# task-wizard has its own GCP project/pool/provider trusting it.
serviceConnectionId: 'gcp-google-play'
packageName: app.taskwiz
track: internal
workloadIdentityProvider: 'projects/1037008586878/locations/global/workloadIdentityPools/ado-pool/providers/ado-provider'
serviceAccountEmail: 'play-release@task-wizard-490917.iam.gserviceaccount.com'
Loading