-
Notifications
You must be signed in to change notification settings - Fork 507
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.
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
Deploy to Staging Firebase App Distribution via CI #1044
Comments
FYI @joshdholtz @crazybob @augustinreille |
This item has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This item has been automatically closed as stale. |
Example success: https://github.com/WorldHealthOrganization/app/actions/runs/155730242 Affects #1044 Unrelatedly, adds a security check to our gradle wrappers. Read more here: https://github.com/marketplace/actions/gradle-wrapper-validation ---- ### Execution On every push to `master`, an Android APK will be pushed to the Firebase App Distribution staging environment using the `client-distribute-staging` workflow. Firebase will invite all members of the `every-build` testing group to test each of these builds. ### Setup 1. [x] (First time) Create [a service account](https://console.cloud.google.com/iam-admin/serviceaccounts/details/104111540645440452578?project=who-myhealth-staging) on `who-myhealth-staging` GCP with `Firebase App Distribution Admin` role. 2. [x] Create a Key for that service account: Add Key -> Create New Key -> JSON. Save the JSON file locally as `key.json`. 3. [x] Generate a random passphrase. Store that passphrase as GitHub secret `FIREBASE_APPDEPLOY_STAGING_SVCACCT_PASSPHRASE`. 4. [x] Encrypt and encode the key using the generated passphrase: gpg --symmetric --cipher-algo AES256 --armor < key.json | base64 5. [x] Store the encrypted key as GitHub secret `FIREBASE_APPDEPLOY_STAGING_SVCACCT_JSON`. 6. [x] Delete the older key on the service account on GCP.
This item has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This item has been automatically closed as stale. |
At the moment Android test builds are being sent to Firebase manually. It would be good to be executed via CI. Fastlane likely has support for this.
Please follow this checklist. Please check each appropriate box (put an 'x' or check it after creating the issue).
The text was updated successfully, but these errors were encountered: