Space Automation automation Help

Billing and Limits

Every JetBrains Space subscription plan includes a certain amount of CI credits. The credits are spent when you run your Automation scripts. Each month your amount of CI credits is restored. The amount of CI credits left in the current month is shown on the Administration → Usage → CI credits bar.

How CI credits usage is calculated

One CI credit is equivalent to one minute of work of a container with default resources:

  • 2 vCPUs (2048 CPU units).

  • 7800 MiB of memory.

The usage is calculated based not on actual usage but based on the resources allocated for a certain container. For example, you use a container with cpu = 512 (0.5 vCPU) and memory = 3900. Such a container will cost you 0.5 CI credits per minute: Though it consumes 0.5 vCPU (512 / 2048 = 0.25 CI credits per minute), it also consumes 3900 MiB of memory (3900 / 7800 = 0.5 CI credits per minute). The larger value is taken into account: 0.5 CI credits per minute.

Here is the calculation for containers with minimal, default, and maximal resources.

CPUMemoryCost
Min0.18 vCPU256 MiB or less 0.09 CI credits per minute
10000 CI credits = approx. 1852 hours = 2.57 containers can work nonstop within a month
Default2 vCPU7800 MiB 1 CI credit per minute
10000 CI credits = approx. 166 hours = one container can work 8 hours a day for 5 days a week within a month
Max4 vCPU16 GiB 2 CI credits per minute
10000 CI credits = approx. 83 hours = one container can work 8 hours a day for 10 days

When does container start working

As described in Build environment, running a job implies running additional helper containers, mounting a volume to a container, and cloning the project repository to this volume. Automation starts to withdraw CI credits from your balance at the moment when cloning of the repository is started. The work of additional helper containers is not taken into account.

What happens when you spend all of your CI credits

Each subscription plan includes not only a certain amount of CI credits but also a certain amount of so-called Reserve credits – your safety stock of CI credits. After you spend all monthly CI credits, Automation will disable automatic job triggers in all repositories (for example, by 'git push'). After this, you can trigger an Automation job only by manually running it on the Automation page. Reserve credits will be used to pay for this job execution.

After you spend all of the Reserve credits, Automation will be disabled. The only option to enable it back is to buy additional CI credits.

Last modified: 27 July 2020