-
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: Expensify.cash 2021-08-11 #4554
Comments
Locking this per the testing steps from #4274 |
@roryabraham Looks like Desktop deploy failed in most PRs. We will hold on desktop regression until it's resolved. |
Checking off #4477, tests pass |
Starting QA 🚀 |
@AndrewGable iOS build is 1.0.84-5, should we hold until .85-0? |
Our last iOS staging deploy failed, but I think it may have been a fluke. So given the following two facts:
That means that in this case you should be fine to run iOS QA on |
Now we're seeing a bunch of duplicate issues on the checklist, and I'm pretty sure it's because of the repo rename. I'm going to try and cleanup the issue and it should be resolved going forward. |
Regression for Web iOS and Android is finished.
I checked off some PRs that were a pass (and only required Web QA). Unchecked PRs still need to be checked in desktop once the build is fixed. |
@isagoico - Fixes for the following blockers have been CP'ed, can you test them again please? The new build is v1.0.85-3 |
Removed a bunch of automated PRs from this checklist. The bug should be fixed now so hopefully they don't come back... |
When retesting #4599 the app is crashing when I typo something on the password text box. #4599 (comment) |
#4597 (comment) retest was a pass, checking it off |
#4628 retest was a pass checking it off. |
Regression is finished (desktop)
PRs that are still failing or need QA:
|
Checking off #4608, in the hope that the race condition has been resolved unknowingly. See this comment for additional info: #4608 (comment) |
@isagoico that sounds good, checked off! |
Only thing to check off is #4610 @marcaaron We good to check it off? |
Are those changes on staging? If so, then we should not deploy a release with them. There is a bug in Onyx that must be fixed first. |
If not, then this should only block the next deploy and not this one. I'm pretty confused because the PR is showing up on this deploy list but I don't actually think the changes are on staging. |
I think no, they're not in staging but @roryabraham @AndrewGable could you double check? |
It looks like 4610 was added in a botify comment, so I believe that was part of the CP bug and it isn't a deploy blocker. The hash on staging is set to the previous hash from before the change so I would say this isn't a deploy blocker and we can check it off. |
Looks like all deploy blockers and PRs have been taken care of 🎉 We should be good to trigger a prod deploy. |
Release Version:
1.0.85-8
Compare Changes: production...staging
This release contains changes from the following pull requests:
View open jobs
URL to click through to E/App open issues instead of Upwork jobs #4516Deploy Blockers:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: