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 2022-04-08 #8566

Closed
17 tasks done
roryabraham opened this issue Apr 8, 2022 · 18 comments
Closed
17 tasks done

Deploy Checklist: New Expensify 2022-04-08 #8566

roryabraham opened this issue Apr 8, 2022 · 18 comments
Assignees
Labels
🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging Monthly KSv2 StagingDeployCash

Comments

@roryabraham
Copy link
Contributor

roryabraham commented Apr 8, 2022

Release Version: 1.1.54-1
Compare Changes: production...staging

This release contains changes from the following pull requests:

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.

cc @Expensify/applauseleads

@mvtglobally mvtglobally added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Apr 8, 2022
@OSBotify
Copy link
Contributor

OSBotify commented Apr 8, 2022

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

@mvtglobally
Copy link

Regression completed
Blocker - #8570

Issues logged
#8497
#8501
#8519
#8520
#8534
#8545
#8572
#8507
#8537
#8541
#8573
#8574

@Julesssss
Copy link
Contributor

The single deploy blocker is being discussed here.

@Julesssss
Copy link
Contributor

Marking the deploy-blocker as resolved, now that the fix is merged (and imminently going to be cherry-picked)

@OSBotify
Copy link
Contributor

👏 Heads up @Expensify/applauseleads 👏
A new pull request has been 🍒 cherry-picked 🍒 to staging, and will be deployed to staging in version 1.1.54-1 🚀

@OSBotify
Copy link
Contributor

🎉 All set?…You bet! @Expensify/applauseleads https://github.com/Expensify/App/releases/tag/1.1.54-1 has been deployed to staging 🎉

@mvtglobally
Copy link

@Julesssss It doesn't look like the fix has been deployed yet on all platforms, can you confirm we are good to check or wait? #8599

@Julesssss
Copy link
Contributor

Hey @mvtglobally. Ah, thanks for mentioning that, it looks like we have an issue with the cherry-pick. I'll ping you once it's ready, but this will likely be tomorrow now.

@melvin-bot melvin-bot bot added the Monthly KSv2 label Apr 11, 2022
@Julesssss
Copy link
Contributor

Hey @mvtglobally, I believe this is now deployed to staging on all platforms.

@Stutikuls
Copy link

Stutikuls commented Apr 12, 2022

Checked all PRs and creating accessibility issues for all PRs where accessibility issue was found.
The non-applicable PRs are - #7807, #8518, #8542
Logged Issues- #8478 , #8479, #8480 , #8430, #8463, #8616

@mvtglobally
Copy link

@Julesssss CP is Pass. We are good to deploy it seems

@Julesssss
Copy link
Contributor

:shipit:

@OSBotify OSBotify reopened this Apr 12, 2022
@OSBotify
Copy link
Contributor

This issue either has unchecked items or has not yet been marked with the :shipit: emoji of approval.
Reopening!

@Julesssss
Copy link
Contributor

Julesssss commented Apr 12, 2022

Ah, new checks.

So unfortunately it looks like we're seeing a new exception with Android version 1.1.54. Same exception is occuring on iOS too.

It's non-fatal, so the user shouldn't notice this. But just to be safe I'm going to bring this up on the PR which I believe introduced the issue.

@Julesssss
Copy link
Contributor

Confusingly, none of the above PRs seem related to the new issue 😕

My best guess is this PR from a couple of versions ago, which refactored the function which is listed as the origin of this new exception. It looks like we're attempting to call these functions before they are defined, but I can't point to a specific recent change.

@Julesssss
Copy link
Contributor

With the occurrences spiking on a single day and no specific code changes which directly modified the problematic area, I think it's okay to continue with the release and I'll submit a quick PR to protect from this crash.

@Julesssss
Copy link
Contributor

Okay, second attempt to deploy

@Julesssss
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 Monthly KSv2 StagingDeployCash
Projects
None yet
Development

No branches or pull requests

6 participants