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 2026-01-07] Remote builds cache: integrate into Adhoc builds #62296
Here’s a high-level overview of our approach to integrating Adhoc build support into our pipeline. The implementation will be divided into two separate pull requests:
First PR:
We’ll begin by updating our existing GitHub Actions to support triggering remote builds for Adhoc. This will be handled as part of the CI process when a pull request is merged into the main branch.
Essentially, we’ll extend the following GitHub Actions workflows to support Adhoc build logic: remote-build-ios.yml, remote-build-android.yml
The goal here is to automatically prepare an Adhoc-ready build artifact as part of our mainline build process.
Second PR:
In the second pull request, we’ll update a manual GitHub Action to upload the Adhoc build (retrieved from the cached result of the first PR’s remote build) to S3 storage.
The action will:
Locate and retrieve the cached build artifact from the prior remote build.
Upload it to a designated S3 bucket for distribution.
Since we will be reusing an already-built artifact, the upload process should be very fast, with minimal build time required.
Let me know if you have any questions or suggestions, thanks!
I'd also like to ensure that if a PR changes native code, then we run an AdHoc build on that PR, the native bundle for that AdHoc build is cached such that subsequent builds of the same branch that change only JS code will also be fast.
We moved the discussion to Slack. We have to decide exactly when we want to trigger the builds as it is a different flow from what we currently have with the dev builds
changed the title [-]Remote builds cache: integrate into Adhoc builds[/-][+][Due for payment 2026-01-07] Remote builds cache: integrate into Adhoc builds[/+]on Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
rinej commentedon Jun 2, 2025
Hello, I'm Tomek from Callstack - I would like to work on this issue
cc @roryabraham
roryabraham commentedon Jun 2, 2025
assigning myself so I can easily follow along, answer questions, and get tagged in reviews
rinej commentedon Jun 5, 2025
Hi Rory,
Here’s a high-level overview of our approach to integrating Adhoc build support into our pipeline. The implementation will be divided into two separate pull requests:
First PR:
We’ll begin by updating our existing GitHub Actions to support triggering remote builds for Adhoc. This will be handled as part of the CI process when a pull request is merged into the main branch.
Essentially, we’ll extend the following GitHub Actions workflows to support Adhoc build logic:
remote-build-ios.yml, remote-build-android.yml
The goal here is to automatically prepare an Adhoc-ready build artifact as part of our mainline build process.
Second PR:
In the second pull request, we’ll update a manual GitHub Action to upload the Adhoc build (retrieved from the cached result of the first PR’s remote build) to S3 storage.
The action will:
Let me know if you have any questions or suggestions, thanks!
cc @adhorodyski
roryabraham commentedon Jun 6, 2025
I'd also like to ensure that if a PR changes native code, then we run an AdHoc build on that PR, the native bundle for that AdHoc build is cached such that subsequent builds of the same branch that change only JS code will also be fast.
rinej commentedon Jun 17, 2025
We moved the discussion to Slack. We have to decide exactly when we want to trigger the builds as it is a different flow from what we currently have with the dev builds
roryabraham commentedon Jul 22, 2025
Posted a follow-up slack convo here: https://expensify.slack.com/archives/C01GTK53T8Q/p1753228474755499
adhorodyski commentedon Aug 1, 2025
Not overdue, resolving CI errors with @rinej ona RNEF bump PR.
69 remaining items
LukasMod commentedon Dec 30, 2025
PR merged #78533
Current thread: https://callstack-hq.slack.com/archives/C05LX9D6E07/p1767052705171319
Fresh build after merge: https://github.com/Expensify/App/actions/runs/20596692632 - 33m 43s total
Cached build after merge: https://github.com/Expensify/App/actions/runs/20597496988 - 5m 59s total
LukasMod commentedon Dec 30, 2025
@mountiny Not sure about this one and parent issue. Do you want to keep these for a while and do more tests or can it be closed?
mountiny commentedon Dec 31, 2025
I think we can close this one, thanks!
[-]Remote builds cache: integrate into Adhoc builds[/-][+][Due for payment 2026-01-07] Remote builds cache: integrate into Adhoc builds[/+]melvin-bot commentedon Dec 31, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Dec 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.89-6 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 2026-01-07. 🎊
For reference, here are some details about the assignees on this issue: