If I deploy using the Vercel CLI, does that count towards the concurrent builds limit?

Help
1

If I deploy using the Vercel CLI, does that count towards the concurrent builds limit?

I could not find the answer to this in the docs: Managing Concurrent Builds

2

@andrewski As per my understanding for Vercel deployments, CLI deployments do count towards the concurrent build limit, just like deployments triggered through Git or the Dashboard. The concurrent build limit is based on the total number of builds happening simultaneously across all deployment methods on your account/team.

You can initiate a Vercel deployment in two ways: with Vercel CLI or by pushing changes to a connected Git repository on GitHub, GitLab, or Bitbucket. It’s also possible for deployments to be initiated through an integration using Vercel REST API.

Depending on how you initiate the build, Vercel may put it in a queue to ensure we build things in the right order and only build the most recent deployment.

Ref: Builds
Why are my Vercel builds queued?

3 Likes
3

Hi @neerajkumar61 , does it also apply when you run vercel deploy with --prebuilt option, e.g. project is built on my own infra?

4

@ulad Yes, vercel deploy --prebuilt does count towards your concurrent build limit. Here’s why:

  1. Even with pre-built files, Vercel still needs to spawn a build container to:
  • Pull your pre-built files
  • Process the deployment
  1. The key difference is efficiency:
  • These pre-built deployments are much faster
  • They occupy the concurrent build slot for a shorter duration compared to regular builds
  • The build container is released more quickly, making the slot available for other deployments

So while it does use a concurrent build slot, the impact is minimal due to the faster processing time of pre-built deployments.

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.