Handling CI minutes

1. You are here:
2. Handling CI minutes

Adding additional CI minutes

From time to time, you may need to grant additional CI minutes to a namespace without affecting the namespace's usual monthly quota.

Purchased CI minutes are not associated with customer's group

To transfer CI minutes from a user's personal namespace to a group namespace, use the Force Association Mechanizer.

There may be times when the Mechanizer does not work and you will need to request a refund for the customer:

• Confirm that the CI minutes are associated with the user's personal namespace.
• Verify if the CI minutes associated with the personal namespace have been consumed. You can check this under Usage Quotas in the users personal profile.  Note: If CI minutes are assigned to a personal namespace with no project or pipeline, this page will show 0/Not supported minutes has been consumed.
  • If they have not been consumed, inform the customer that they've selected their personal namespace instead of their group by mistake (while purchasing the CI minutes) and pass the ticket to the billing team to process the refund. The customer can then repurchase the CI minutes for their group.
  • If they have been consumed, they're not eligible for a refund - inform the customer that they're already using the purchased CI minutes pack and redirect the customer to purchase a new CI minutes pack corresponding to their group.

GitLab.com group is not visible during the purchase

• While purchasing the CI minutes, the billing page shows a drop-down menu to choose the accurate namespace with which the CI minutes should be associated. In case if the user is unable to view and choose the desired group during the purchase, most probably the user is not an owner of that group - reply to the user stating that they need to either get their permissions updated(to owner) to be able to choose the group on the billing page (or) an existing owner of the group can purchase the CI minutes using their customer portal account.