Skip to Content

Limits

How many runners and vCPUs your organization runs at once, the largest build size, and how to ask for more.

Each organization has three capacity limits, shown on the Limits tab of the Actions page:

  • Concurrent jobs: how many runners run at once.
  • Concurrent vCPUs: how many vCPUs those runners use together. Runners get 4 GB of RAM per vCPU.
  • Max build size: the largest vCPU and memory one build may use.

Limits grow automatically with your paid usage. Jobs above a limit wait in the queue until a runner frees up.

Requesting higher limits

Organization owners and admins can click Request higher limits on the Limits tab. Pick what to raise:

  • Concurrency: concurrent jobs and vCPUs, in whole numbers (up to 64 jobs and 160 vCPUs). The RAM that comes with the vCPUs is shown for reference.
  • Build size: vCPU and memory in GB per build, up to the largest build size offered.

Add a short note on what you are running if it helps. The request must ask for more than you have now, and one request of each kind can be open at a time.

A-Line.cloud reviews the request and either raises your limits, possibly to different values than asked, or declines it with a reason. Owners and admins get a notification either way, and the request's status (Pending, Raised or Declined) stays on the Limits tab. After a decision you can send a new request.

On this page