Skip to content

[Due for payment 2026-01-07] Remote builds cache: integrate into Adhoc builds #62296

Closed

Description

@adhorodyski

About
Goal of this is to integrate the GH artifact cache for remote builds (RNEF) into Adhoc builds.
It's a followup to #58743

Expected outcome
As a result, adhoc builds should take ~1.5min after hitting the cache.

Issue OwnerCurrent Issue Owner: @greg-schroeder

Activity

  1. rinej commented on Jun 2, 2025

    @rinej
    Contributor

    Hello, I'm Tomek from Callstack - I would like to work on this issue

    cc @roryabraham

  2. roryabraham commented on Jun 2, 2025

    @roryabraham
    Contributor

    assigning myself so I can easily follow along, answer questions, and get tagged in reviews

  3. rinej commented on Jun 5, 2025

    @rinej
    Contributor

    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:

    • 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!

    cc @adhorodyski

  4. roryabraham commented on Jun 6, 2025

    @roryabraham
    Contributor

    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.

  5. rinej commented on Jun 17, 2025

    @rinej
    Contributor

    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

  6. roryabraham commented on Jul 22, 2025

    @roryabraham
    Contributor
  7. adhorodyski commented on Aug 1, 2025

    @adhorodyski
    ContributorAuthor

    Not overdue, resolving CI errors with @rinej ona RNEF bump PR.

  8. 69 remaining items

  9. self-assigned this
    on Dec 29, 2025
  10. LukasMod commented on Dec 30, 2025

    @LukasMod
    Contributor
  11. LukasMod commented on Dec 30, 2025

    @LukasMod
    Contributor

    @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?

  12. mountiny commented on Dec 31, 2025

    @mountiny
    Contributor

    I think we can close this one, thanks!

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 31, 2025
  14. 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
  15. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  16. melvin-bot commented on Dec 31, 2025

    @melvin-bot

    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:

    • @rinej does not require payment (Contractor)
    • @akinwale requires payment through NewDot Manual Requests
    • @LukasMod does not require payment (Contractor)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions