Replies: 1 comment
-
|
Hi, it sounds like you're describing exactly how Remote Caching works. We check the Remote Cache to see if the task has run before with the same inputs before running it. If the task exists in Remote Cache, it's a cache hit and we replay the cached work. Can you provide more details if you're meaning something else? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
Non-goals
-
Background
I have a heavy compilation job that runs on github CI and uploads the artifacts to the Vercel's remote cache. The artifacts are needed for my frontend app (vite or nextjs) to be built and published on Vercel. It would be cool if it was possible for Vercel to somehow wait for the remote cache before starting the build of my frontend app.
Proposal
TURBO_WAIT_FOR_REMOTE_CACHE=1 turbo build- waits for the remote cache of all tasks before proceeding with building.Beta Was this translation helpful? Give feedback.
All reactions