Skip to content
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

Closed
2 tasks done
kassim opened this issue Apr 15, 2020 · 5 comments · May be fixed by #1293
Closed
2 tasks done

Deploy to Staging Firebase App Distribution via CI #1044

kassim opened this issue Apr 15, 2020 · 5 comments · May be fixed by #1293
Assignees
Labels
dev-workflow Developer productivity, CI, builds, and/or processes help wanted Volunteers needed! Comment on this issue if you can work on it. resolved:stale No recent activity on the issue or PR

Comments

@kassim
Copy link
Contributor

kassim commented Apr 15, 2020

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).

@advayDev1 advayDev1 added the needs:triage New issue that needs triage label Apr 17, 2020
@brunobowden
Copy link
Collaborator

FYI @joshdholtz @crazybob @augustinreille

@advayDev1 advayDev1 added dev-workflow Developer productivity, CI, builds, and/or processes help wanted Volunteers needed! Comment on this issue if you can work on it. and removed needs:triage New issue that needs triage labels Apr 19, 2020
@epicfaace epicfaace self-assigned this May 13, 2020
@epicfaace epicfaace changed the title Deploy to Firebase Beta Distribution via CI Deploy to Firebase App Distribution via CI May 13, 2020
@stale
Copy link

stale bot commented Jun 19, 2020

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.

@stale stale bot added the resolved:stale No recent activity on the issue or PR label Jun 19, 2020
@stale
Copy link

stale bot commented Jun 26, 2020

This item has been automatically closed as stale.

@stale stale bot closed this as completed Jun 26, 2020
@epicfaace epicfaace reopened this Jun 26, 2020
@stale stale bot removed the resolved:stale No recent activity on the issue or PR label Jun 26, 2020
@advayDev1 advayDev1 changed the title Deploy to Firebase App Distribution via CI Deploy to Staging Firebase App Distribution via CI Jul 2, 2020
advayDev1 added a commit that referenced this issue Jul 7, 2020
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.
@stale
Copy link

stale bot commented Aug 3, 2020

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.

@stale stale bot added the resolved:stale No recent activity on the issue or PR label Aug 3, 2020
@stale
Copy link

stale bot commented Aug 10, 2020

This item has been automatically closed as stale.

@stale stale bot closed this as completed Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-workflow Developer productivity, CI, builds, and/or processes help wanted Volunteers needed! Comment on this issue if you can work on it. resolved:stale No recent activity on the issue or PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants