-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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 Checklist: New Expensify 2021-08-25 #4828
Comments
Starting QA 🚀 |
Removing the lock label to fix staging deploys |
Everything was a pass here 🎉 https://github.com/Expensify/App/actions/runs/1168597268 |
Yes, those will not appear because of the bug that existed when we ran the prod deploy. Ignore and begin QA please. |
Starting QA 🚀 |
#4793 (comment) Resolved - Checking it off |
#4871 (comment) fixed #4868 🎉 Checking them off |
Before we close this issue, we should really do some testing of this PR. |
Checking off #4608 pending prod deploy. |
This issue either has unchecked QA steps or has not yet been marked with the |
@roryabraham I think #4824 has to be tested when it hits production (not sure.) |
Just FYI there are a number of issues with the deploy process we are working to address. |
Going to close this to verify that it reopens w/ a comment. |
This issue either has unchecked QA steps or has not yet been marked with the |
Nice, that worked as expected. |
@isagoico Can you please close this issue w/o any comment for me? |
Sorry, only members of @Expensify/Mobile-Deployers can close deploy checklists. |
@Expensify/applauseleads There were some issues with our standard deploy process today, and we accidentally ran a production deploy when the issue was closed here. Fortunately, all the code that was deploy was already production-approved, so we got lucky there. 😅 🎉 I am going to remove and re-add the lock label to this checklist, and that will trigger a fresh staging deploy with all the latest changes. It will also add a few PRs to this checklist, which we are going to reuse for the next QA/deploy cycle. Furthermore, we've put some new safeguards in place so that, going forward, only members of @Expensify/mobile-deployers will be able to close out deploy checklists and trigger a production deploy. What does this mean for Applause?
Thanks, and let me know if you have any questions! |
Trying that one more time after merging #4940 |
Okay, staging deploy for |
Starting QA! |
We're almost finished with QA, all PRs have been tested and I already updated the checklist with the results.
#4880 is failing because of #4958 (It's currently being fixed 🎉) On regression, we haven't found any issues or deploy blocker yet. Still about 25% left in the TestRail. CC @roryabraham |
Checking off #4880 since it's a pass 🎉 |
@TomatoToaster is going to QA #4923 internally, but since it's still hidden behind a beta, I'm not going to block the production deploy on it. So I'm going to go ahead and check it off on the checklist and run a prod deploy. |
@roryabraham We're about to finish the regression testing, only 10% left, should be done in a little bit. |
It's finished! feel free to trigger the Prod deploy 🎉 (no deploy blocker were found!) |
Just noting that this one is QA'ed and passed too: #4923 (comment) |
Release Version:
1.0.90-2
Compare Changes: production...staging
This release contains changes from the following pull requests:
currentDate
but we don't use it #4724Deploy Blockers:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: