Is there a way to to skip the build cache in Vercel?

[Blatty]

Hey there,

I'm trying to find out if there's a flag or environment variable to skip the build cache in Vercel? Similar to how it's used in the CLI: https://vercel.com/docs/cli#introduction/global-options/force

[amyegan]

Hi @Blatty. We don't currently have a way to disable the build cache for automated deployments using Vercel for Git integrations, but we do have a few other ways to deploy without build cache:

• Redeploying from the Dashboard will bypass the Build Cache, unless you check the box to include it
• Using the API using the forceNew query parameter to create a new deployment
• Using the CLI with --force option, which you already mentioned

EDIT (14th Oct 2022): The VERCEL_FORCE_NO_BUILD_CACHE env var now exists! Set this to 1 and the build cache will be skipped.

[gf5901]

So I see VERCEL_FORCE_NO_BUILD_CACHE is set so skipping build cache step at the top of the log, but then later on in the log I see:

• Remote computation caching enabled
@unirepo/web:build: cache hit, replaying output 2e0f3c1bfab1a4b7

And it uses the cached build. Then I have to manually redeploy it for it to not use the cached build. Not sure if it's something I configured incorrectly on my side or not, but I'd like it to not cache anything when it deploys to production since production uses different environment variables from my staging environment.

[amyegan]

Do you have a deployment link, public repo, or minimal reproducible example that you can share?

[gf5901]

I do not, should I add you to the project so you can view the deployment link? It's been quite troublesome for me. If I forget to manually redeploy with the build cache turn off, all our users start hitting our QA environment. Is there anyway I can set it to manually kick off builds to production instead of on changes to the main branch?

[Pieparker]

Hey gf5901! This sounds like Remote Caching is enabled. This is expected by default when Turborepo is enabled and isn't controlled by the build cache; they're autonomous.

The above link shows how and where Remote Caching can be toggled within the UI. I do hope that the helps!

[gf5901]

Thanks a ton, @Pieparker! Looks like turning off Remote Caching fixed the issue.

[johnlindquist]

@amyegan Is the forceNew query parameter supported when using deploy hooks?

[deve-sh]

You can use the buildCache query param to do so: https://vercel.com/docs/deployments/deploy-hooks#build-cache