Billing and Limits
Every JetBrains Space subscription plan includes a certain amount of CI credits. The allocated amount is not dependent on the number of members in the organization. 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
7800 MB 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 = 0.5.cpu and memory = 3900.mb. Such a container will cost you 0.5 CI credits per minute: Though it consumes 0.5 vCPU (0.5 / 2 = 0.25 CI credits per minute), it also consumes 3900 MB 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.
| CPU | Memory | Cost | |
|---|---|---|---|
| Min | 0.18 vCPU | 256 MB or less | 0.09 CI credits per minute 10000 CI credits = approx. 1852 hours = 2.57 containers can work nonstop within a month |
| Default | 2 vCPU | 7800 MB | 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 |
| Max | 4 vCPU | 15.6 GB | 2 CI credits per minute 10000 CI credits = approx. 83 hours = one container can work 8 hours a day for 10 days |
File share limits
The file share has the following limitations:
The file share size is limited to 2 GB within a job. Learn more
The file share monthly traffic limit is 200 GB for all subscription plans. Learn more
Limitations of the Free plan
As a response to the increasing attempts to use Space Automation for cryptomining, we have introduced additional limitations for the Free subscription plan. The maximum allowed number of concurrently running steps on the Free plan is 10. This limit is applied to the entire organization.
For example, let's assume that at the moment Automation runs five steps: These can be five jobs with a single step, one job with five steps inside the parallel block, or some other combination. At the same time, a job with six parallel steps is triggered. Automation will not run this job, because in this case the number of concurrently running steps would exceed 10.
When does container start working
As described in Check-Out Project Source Code, 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 run.
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.
How many CI credits does a certain step spend
Open the project's Jobs page.
Select the job you are interested in.
Open the Steps tab.
Choose the required step and switch to the Details tab.
The amount of CI credits spent on this step are shown in Credits spent:
