You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-02-10] Create workflow to compare newDot and hybridApp builds so we can improve the build times #56063
The hybridApp builds are noticeably slower than the standalone NewDot native builds, this is hindering our ability to test and ship code fast as well as debug different branched (bisect on native changes etc)
Solution
Create workflow that will allow us to simply run and compare the standalone and hybrid app builds from main in github CI so we can analyze where to get improvements in the build time
⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️
changed the title [-]Create workflow to compare newDot and hybridApp builds so we can improve the build times[/-][+][Due for payment 2025-02-10] Create workflow to compare newDot and hybridApp builds so we can improve the build times[/+]on Feb 3, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.93-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@war-in] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Jan 30, 2025
Triggered auto assignment to @isabelastisser (
NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.melvin-bot commentedon Jan 30, 2025
melvin-bot commentedon Jan 30, 2025
Triggered auto assignment to Design team member for new feature review - @dannymcclain (
NewFeature)mountiny commentedon Jan 30, 2025
PR merged
war-in commentedon Jan 30, 2025
Hi, I'm Marcin from Software Mansion and I'm an author of the PR
mountiny commentedon Jan 30, 2025
No payments or regression testing will be required, gonna close this once deployed without issues
[-]Create workflow to compare newDot and hybridApp builds so we can improve the build times[/-][+][Due for payment 2025-02-10] Create workflow to compare newDot and hybridApp builds so we can improve the build times[/+]melvin-bot commentedon Feb 3, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 3, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.93-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-02-10. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Feb 3, 2025
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed: