Skip to content

Compute minutes administration

DETAILS: Tier: Premium, Ultimate Offering: Self-managed, GitLab Dedicated

  • Renamed from "CI/CD minutes" to "compute quota" or "compute minutes" in GitLab 16.1.

Administrators can limit the amount of time that projects can use to run jobs on instance runners each month. This limit is tracked with a compute minutes quota. Project runners are not subject to the compute quota.

On self-managed GitLab instances:

  • Compute quotas are disabled by default.
  • Administrators can assign more compute minutes if a namespace uses all its monthly quota.
  • The cost factors are:
    • 0 for public projects, so they do not consume compute minutes.
    • 1 for internal and private projects.

Trigger jobs do not execute on runners, so they do not consume compute minutes, even when using strategy:depend to wait for the downstream pipeline status. The triggered downstream pipeline consumes compute minutes the same as other pipelines.

GitLab.com administrators can add a namespace to the reduced cost factor with the ci_minimal_cost_factor_for_gitlab_namespaces feature flag.

Set the compute quota for all namespaces

By default, GitLab instances do not have a compute quota. The default value for the quota is 0, which is unlimited.

Prerequisites:

  • You must be a GitLab administrator.

To change the default quota that applies to all namespaces:

  1. On the left sidebar, at the bottom, select Admin.
  2. Select Settings > CI/CD.
  3. Expand Continuous Integration and Deployment.
  4. In the Compute quota box, enter a limit.
  5. Select Save changes.

If a quota is already defined for a specific namespace, this value does not change that quota.

Set the compute quota for a group

You can override the global value and set a compute quota for a group.

Prerequisites:

  • You must be a GitLab administrator.
  • The group must be a top-level group, not a subgroup.

To set a compute quota for a group or namespace:

  1. On the left sidebar, at the bottom, select Admin.
  2. Select Overview > Groups.
  3. For the group you want to update, select Edit.
  4. In the Compute quota box, enter the maximum number of compute minutes.
  5. Select Save changes.

You can also use the update group API or the update user API instead.

Reset compute usage

An administrator can reset the compute usage for a namespace for the current month.

Reset usage for a personal namespace

  1. Find the user in the Admin area.
  2. Select Edit.
  3. In Limits, select Reset compute usage.

Reset usage for a group namespace

  1. Find the group in the Admin area.
  2. Select Edit.
  3. In Permissions and group features, select Reset compute usage.