-
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 2022-10-19 #11979
Comments
#10585 checked, to old to be blocker over a month and a half, weird. |
🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.2.18-1 🚀 |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-2 has been deployed to staging 🎉 |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-3 has been deployed to staging 🎉 |
checking #11633, it's already in prod so not a blocker. |
checking #11983, hard to reproduce, maybe connection issue. not a blocker |
checking #12000, was reproduced in Prod by @ctkochan22. |
@thienlnam removed the blocker for #12012 so checking that one as well |
@sketchydroide |
👏 Heads up @Expensify/applauseleads 👏 |
Did you get those right @mvtglobally, they are both the same, and seems to be about a Web change |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-4 has been deployed to staging 🎉 |
Checking #12035 and #12037 off as @trjExpensify confirmed that the fixed worked. |
Should #11796 be tagged as deployBlocker and added to the deployBlockerList since we mentioned it is blocking this #11640? I'm just confused because #11640 says to connect with "Chase" via Plaid and not "Fidelity". cc @mvtglobally |
@PauloGasparSv the PR was created a long time ago when we used Chase to test. Now Chase is blocked for a while, so we use Fidelity. |
#11995 was closed, we can't replicate it anymore, maybe it was a backend issue. |
#12009 was also closed, we can't replicate it anymore. checking it off |
@mvtglobally |
@Expensify/applauseleads we decided to CP #11944 because it fixes some critical bugs and we wanted to get it out over the weekend. Let's make sure we complete QA for that before proceeding to deploy production |
We are on it |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-5 has been deployed to staging 🎉 |
@roryabraham @sketchydroide Seeing few issues with new PR. Team is checking if any blockers and logging in a bit |
@roryabraham @sketchydroide I think iOS build failed there so the fix is not in testflight for iOS yet (I cannot test on android unfortunately) |
Retrying the iOS deploy now |
@sketchydroide @roryabraham #12013 is only failing with #12061. Since thats not a blocker, I guess we can check it off. PR. #11944 is failing with #11867. Its an older KI. @mountiny Android Build is updated |
Correct @mvtglobally this is also ok, the issue mentioned should not be solved by this change. We thought it might and but it has a different root cause, updated the PR body there. |
Still no IOS build |
Working on it, just put up #12068 to try and fix it |
👏 Heads up @Expensify/applauseleads 👏 |
Still working on iOS deploys, another PR here |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-6 has been deployed to staging 🎉 |
👏 Heads up @Expensify/applauseleads 👏 |
Yet another deploy running here, hopefully this one works 🤞🏼 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-7 has been deployed to staging 🎉 |
Unfortunately, still no IOS |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-9 has been deployed to staging 🎉 |
@roryabraham @chiragsalian PR #11944 is pass on IOS. #11867 & #10290 Not blockers, so checking off. Asked team to double check this #12067. Only 1 out of 5 testers was able to repro originally. |
okay thank you |
@chiragsalian Record_2022-10-24-21-37-54_4f9154176b47c00da84e32064abf1c48.mp4 |
Strange, yeah i was just able to reproduce the issue using sahil's credentials posted here. And i can reproduce only on staging and not on production. Investigating. |
We think we found the fix (or rather revert) to address the deploy blocker. We're waiting for it to hit staging and deploy to devices before re-testing. |
👏 Heads up @Expensify/applauseleads 👏 |
🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.2.18-10 has been deployed to staging 🎉 |
Release Version:
1.2.18-10
Compare Changes: production...staging
This release contains changes from the following pull requests:
Deploy Blockers:
Deployer verifications:
cc @Expensify/applauseleads
The text was updated successfully, but these errors were encountered: