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 Checklist: New Expensify 2023-08-21 #25625

Closed
OSBotify opened this issue Aug 21, 2023 · 54 comments
Closed

Deploy Checklist: New Expensify 2023-08-21 #25625

OSBotify opened this issue Aug 21, 2023 · 54 comments
Assignees
Labels
🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging StagingDeployCash Weekly KSv2

Comments

@OSBotify
Copy link
Contributor

OSBotify commented Aug 21, 2023

Release Version: 1.3.56-24
Compare Changes: production...staging

This release contains changes from the following pull requests:

Internal QA:

Deploy Blockers:

Deployer verifications:

  • I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
  • I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
  • I checked GitHub Status and verified there is no reported incident with Actions.

cc @Expensify/applauseleads

@mountiny
Copy link
Contributor

#23626 this is from previous deploy

@mvtglobally mvtglobally added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Aug 21, 2023
@OSBotify
Copy link
Contributor Author

🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.56-0 🚀

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 labels Aug 22, 2023
@roryabraham roryabraham removed Reviewing Has a PR in review 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Aug 22, 2023
@roryabraham
Copy link
Contributor

Unlocking this because staging deploys are broken. We hopefully fixed them but need to trigger a full deploy from main. Slack context: https://expensify.slack.com/archives/C03V9A4TB/p1692661899493529

@roryabraham
Copy link
Contributor

New staging deploy running here, re-locking this checklist.

@roryabraham roryabraham added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Aug 22, 2023
@OSBotify
Copy link
Contributor Author

🚀 All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.56-2 🚀

@sakluger
Copy link
Contributor

@roryabraham I went through the list of blockers and categorized them by status to help you out a bit! 🆗 means that the deployblocker label was removed (I checked these off above). ✔️ means that the linked PR was merged (I'm not sure if it's okay to check these off above yet). 📋 means that there is a PR in review but not merged. ❗ means that the issue either has no PR yet or is unassigned.

🆗 #25481 - Likely fixed, deploy blocker label removed
✔️ #25616 - PR merged
🆗 #25626 - NAB
🆗 #25637 - NAB (dupe of another issue)
✔️ #25640 - PR merged
📋 #25644 - PR merged
🆗 #25647 - NAB
✔️ #25648 - PR merged
📋 #25649 - PR in review
✔️ #25650 - PR merged
#25673 - No PR
📋 #25674 - PR in review
#25676 - No PR
#25678 - PR merged
📋 #25679 - Draft PR
🆗 #25680 - NAB
🆗 #25683 - Closed
#25685 - No PR
#25686 - No PR
#25688 - No PR
#25690 - No PR, unable to repro in DEV
🆗 #25692 - NAB
#25694 - No PR
#25696 - No PR
#25697 - No PR
#25698 - No PR
#25705 - No PR

@roryabraham
Copy link
Contributor

roryabraham commented Aug 22, 2023

Ok, let's check back in. Going to use a similar system as @sakluger:

❗ – no status
🆗 – demoted / NAB
📋 – solution in progress
🏁 – solution merged + CP'd, needs retest
✅ – resolved


#25481
🏁 #25616, should be fixed by #25613 in 1.3.56-7
🆗 #25626
🏁 #25637, this was closed in favor of #25638, but should be fixed by #25645 in 1.3.56-10
🏁 #25640, should be fixed by #25684 in 1.3.56-8
🏁 #25644, solution CP'd to staging in 1.3.56-9
🆗 #25647
🏁 #25648, solution CP'd to staging in 1.3.56-9
📋 #25649, may be fixed by #25660
🏁 #25650, should be fixed by #25665 in 1.3.56-3
#25673
🏁 #25674, should be fixed (or rather, made irrelevant) by #25516 in 1.3.56-4
#25676
🏁 #25678, should be fixed by #25691 in 1.3.56-9
#25679, fixed by #25706 in 1.3.56-14
🆗 #25680
🆗 #25683
🏁 #25685, should be fixed by #25738 in 1.3.56-18
#25686
#25688
🏁 #25690, should be fixed by #25724 in 1.3.56-15
🆗 #25692
#25694
🆗 #25696
🏁 #25697, should be fixed by #25710 in 1.3.56-11
#25698
🏁 #25705, should be fixed by #25734 in 1.3.56-17
#25713
🏁 #25715, should be fixed by #25719 in 1.3.56-13
🆗 #25717
🏁 #25718, should be fixed by #25726 in 1.3.56-16
📋 #25728, should be fixed by #25741, needs review
🏁 #25737, should be fixed by #25772 in 1.3.56-19


The following PRs have been CP'd for this checklist:

These should be automatically added to the checklist but due to a known 🐛 are not, so I'm going to manually add them and update the version on the checklist accordingly.

@mvtglobally
Copy link

@roryabraham TR Regression is completed we are wrapping last CPs/PRs

Current PR summary
#23673 is failing #25697 & #25679
#24301 is failing #25683
#24306 is failing #25696
#24235 - Pending validation on all platforms
#24346 - passed on Web/MWeb, not able to validate on Desktop/Native. Ok to check off?
#24379 - Pending validation on all platforms
#24512 - failing #24265. repro in PROD
#24513 - failing #23813.
#24525 - Pending validation on all platforms
#24571 & #25504 - PROD QA. Ok to check off?
#24577 - Failing #24516
#24625 - failing #21210, repro in prod checking off
#24637 - Blocked due to #18375. Can you QA internally?
#24638 - Pending validation on all platforms
#24643 - failing #25717
#24640 - Pending validation on all platforms
#25158 - Pending validation on all platforms
#25399 - Failing #22640
#25426 (comment) - Ok to check off?
#25476 - failing #25441
#25506 - Failing #25674 & #25696
#25691 - failing #25767
#25706 - failing #25679
#25734 - Pending validation on all platforms
#25738 - Pending validation on all platforms

@amyevans
Copy link
Contributor

I checked off #25679 after its PR was cherry-picked and I retested on staging.

@luacmartins
Copy link
Contributor

Checking off #25767. The feature is still a WIP, we're aware of it and have a PR in review to fix it.

@lindboe
Copy link
Contributor

lindboe commented Aug 23, 2023

We made a fix for #25697, but it looks like that isn't tracked here -- do we need to do anything to get this into staging @roryabraham?

@mountiny
Copy link
Contributor

Checking #25737 off, fixed in staging

@roryabraham
Copy link
Contributor

roryabraham commented Aug 23, 2023

We made a fix for #25697, but it looks like that isn't tracked here -- do we need to do anything to get this into staging @roryabraham?

@lindboe there's a known 🐛 that causes cherry-picked PRs to not automatically appear on the checklist. In general you shouldn't need to do anything to have them appear.

In this case, I did manually add the fix to the checklist I believe: #25710

@luacmartins
Copy link
Contributor

Checking off #25784. Not repro on main anymore, the feature is still a WIP and the bug doesn't affect App functionality.

@roryabraham
Copy link
Contributor

#25649 is a valid bug but not bad enough to block deploy imo. Going to check it off.

@luacmartins
Copy link
Contributor

Checking off #25686 since it was demoted to NAB.

@luacmartins
Copy link
Contributor

Checking off #25694. This is the intended behavior and we are changing the default merchant name here

@mountiny
Copy link
Contributor

Checking #25616 off its fixed

@roryabraham
Copy link
Contributor

Checking off #25676, not reproducible

@mountiny
Copy link
Contributor

checking #25476 off based on this comment #25441 (comment) tested just now

@roryabraham
Copy link
Contributor

Demoted #25713, checking it off

@roryabraham
Copy link
Contributor

#25718 is fixed, checking it off

@roryabraham
Copy link
Contributor

#25728 is fixed, checking it off

@aldo-expensify
Copy link
Contributor

#25705 is fixed, just tested it, checking it off

@roryabraham
Copy link
Contributor

We are CPing #25789 to fix #25768 in 1.3.56-21

@roryabraham
Copy link
Contributor

#25776 is expected behavior, checking it off

@roryabraham
Copy link
Contributor

#25679 and #25697 are resolved, checking off #23673

@roryabraham
Copy link
Contributor

#25683 is resolved, checking off #24301

@roryabraham
Copy link
Contributor

#25696 is NAB / being fixed behind a beta. So I'm checking off #24306

@roryabraham
Copy link
Contributor

For #24346, it seems like we don't have deeplinks configured for the routes in question, and it's very unlikely that a first time user will have the app installed anyways. Checking it off

@roryabraham
Copy link
Contributor

#24512 - failing #24265. repro in PROD

Checking this off as NAB. @mvtglobally In the future you can feel free to check these off as long as the issue is documented.

@roryabraham
Copy link
Contributor

#24513 - failing #23813.

Asked for more details in the PR: #24513 (comment)

Going to check this off as NAB, it just doesn't fix the original issue it was meant to fix it seems.

@roryabraham
Copy link
Contributor

#24571 & #25504 - PROD QA. Ok to check off?

Yes, checking these off

@marcaaron
Copy link
Contributor

Demoting #25779. edge case issue imo and not a common flow people would typically be running into.

@roryabraham
Copy link
Contributor

#24577 is a QA fail but not a blocker. Left a comment requesting more details in the PR

@roryabraham
Copy link
Contributor

@marcaaron
Copy link
Contributor

We can check off #25768 after the CP from @dangrous. But we now have #25797 to look at 😄

@roryabraham
Copy link
Contributor

#25399 is a QA fail but not a deploy blocker, checking it off

@roryabraham
Copy link
Contributor

Checking off #25506 as a dupe of #24306

@roryabraham
Copy link
Contributor

As @marcaaron mentioned, #25789 caused another deploy blocker, but we're going to resolve it separately so I'm checking #25789 off

@roryabraham
Copy link
Contributor

Demoting #25787

@roryabraham
Copy link
Contributor

Demoting #25803 and checking it off

@roryabraham
Copy link
Contributor

#25673 is not reproducible and ultimately a somewhat minor bug that doesn't affect usability. Demoting it and checking it off

@marcaaron
Copy link
Contributor

Internal QA on #24637

@roryabraham
Copy link
Contributor

#25797 is passing on staging now ✅ , checking it off along with #25799

@roryabraham
Copy link
Contributor

#25688 is passing on staging now ✅, checking it off along with #25806

@roryabraham
Copy link
Contributor

:shipit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging StagingDeployCash Weekly KSv2
Projects
None yet
Development

No branches or pull requests