acetheking987/bsky-social-app
1
0
Fork 0
Code Issues Actions Packages Projects Releases 1 Wiki Activity

Clarify some things

Browse Source
This commit is contained in:
Eric Bailey
2024-06-04 17:40:03 -05:00
parent e64b7cf698
commit a6c99b1c45
1 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deploy-ota.md
+12 -3
View File
@@ -19,7 +19,7 @@ testing as well as retrieving the build number.
- You should have signed in to EAS locally through npx eas login. You will need to modify the build number in a - You should have signed in to EAS locally through npx eas login. You will need to modify the build number in a
subsequent step. subsequent step.
- Identify the build number of the production app you want to deploy an update for. iOS and Android build numbers are - Identify the build number of the production app you want to deploy an update for. iOS and Android build numbers are
divergent, so you will need to find both divergent, so you will need to find both. Save these build numbers for later steps.
![app-build-number](./img/app-build-number.png) ![app-build-number](./img/app-build-number.png)
@@ -38,14 +38,17 @@ to create your branch from, this should be properly set.
### Deployment ### Deployment
- Update the build number through EAS - Update the build number through EAS to match the build numbers of the
production iOS/Android apps
- Note: This isn’t strictly necessary, but having a step that takes you off of GitHub and into the terminal provides - Note: This isn’t strictly necessary, but having a step that takes you off of GitHub and into the terminal provides
a little “friction” to avoid fat fingering a release. Since there are legitimate reasons to just “click and deploy” a little “friction” to avoid fat fingering a release. Since there are legitimate reasons to just “click and deploy”
for internal builds, I felt it useful to make sure it doesn’t accidentally become a prod deployment. for internal builds, I felt it useful to make sure it doesn’t accidentally become a prod deployment.
- Set the build number to the appropriate build number found in the prerequisite steps. Again, this should be the - Set the build numbers to the values found in the prerequisite steps. Again, this should be the
build number for the current production release you want to deploy for. build number for the current production release you want to deploy for.
- `npx eas build:version:set -p ios` - `npx eas build:version:set -p ios`
- `npx eas build:version:set -p android` - `npx eas build:version:set -p android`
- These steps should spit out what the current build number is, save those values
for later too
- Run the deployment - Run the deployment
- Navigate to https://github.com/bluesky-social/social-app/actions/workflows/bundle-deploy-eas-update.yml - Navigate to https://github.com/bluesky-social/social-app/actions/workflows/bundle-deploy-eas-update.yml
- Select the “Run Workflow” dropdown - Select the “Run Workflow” dropdown
@@ -79,3 +82,9 @@ In about five minutes, the new deployment should be available for download. To t
- Launch the app once and wait approximately 15 seconds - Launch the app once and wait approximately 15 seconds
- Relaunch the app - Relaunch the app
- Check the Settings page and scroll to the bottom. The commit hash should now be the latest commit on your deployed branch. - Check the Settings page and scroll to the bottom. The commit hash should now be the latest commit on your deployed branch.
### Post Deployment
- Reset both platforms build numbers to what they were before the OTA
deployment. These values should have been logged by the EAS CLI when you
reset them to the production values prior to OTA.