Merge branch 'selhorn-runner-minutes1' into 'master'

Docs: Added shared runner minutes

See merge request gitlab-org/gitlab!34799

doc/ci/runners/README.md

@@ -38,9 +38,14 @@ multiple projects.
 If you are using a self-managed instance of GitLab, your administrator can create
 shared Runners and configure them to use the
 [executor](https://docs.gitlab.com/runner/executors/README.html) you want.
+The administrator can also configure a maximum number of Shared Runner [pipeline minutes for
+each group](../../user/admin_area/settings/continuous_integration.md#shared-runners-pipeline-minutes-quota-starter-only).
 
 If you are using GitLab.com, you can select from a list of
 [shared Runners that GitLab maintains](../../user/gitlab_com/index.md#shared-runners).
+You can use Shared Runners for a limited number of
+[minutes](../../subscriptions/index.md#ci-pipeline-minutes) each month, based on
+your [GitLab.com tier](https://about.gitlab.com/pricing/).
 
 #### How shared Runners pick jobs
 

doc/user/admin_area/settings/continuous_integration.md

@@ -18,7 +18,7 @@ To enable (or disable) [Auto DevOps](../../../topics/autodevops/index.md)
 for all projects:
 
 1. Go to **Admin Area > Settings > CI/CD**
-1. Check (or uncheck to disable) the box that says "Default to Auto DevOps pipeline for all projects"
+1. Check (or uncheck to disable) the box that says **Default to Auto DevOps pipeline for all projects**.
 1. Optionally, set up the [Auto DevOps base domain](../../../topics/autodevops/index.md#auto-devops-base-domain)
    which is going to be used for Auto Deploy and Auto Review Apps.
 1. Hit **Save changes** for the changes to take effect.
@@ -48,19 +48,19 @@ To change it at the:
 
    1. Go to **Admin Area > Settings > CI/CD**.
    1. Change the value of maximum artifacts size (in MB).
-   1. Hit **Save changes** for the changes to take effect.
+   1. Click **Save changes** for the changes to take effect.
 
 - [Group level](../../group/index.md#group-settings) (this will override the instance setting):
 
   1. Go to the group's **Settings > CI / CD > General Pipelines**.
   1. Change the value of **maximum artifacts size (in MB)**.
-  1. Press **Save changes** for the changes to take effect.
+  1. Click **Save changes** for the changes to take effect.
 
 - [Project level](../../../ci/pipelines/settings.md) (this will override the instance and group settings):
 
   1. Go to the project's **Settings > CI / CD > General Pipelines**.
   1. Change the value of **maximum artifacts size (in MB)**.
-  1. Press **Save changes** for the changes to take effect.
+  1. Click **Save changes** for the changes to take effect.
 
 NOTE: **Note**
 The setting at all levels is only available to GitLab administrators.
@@ -74,7 +74,7 @@ and the default value is `30 days`.
 
 1. Go to **Admin Area > Settings > CI/CD**.
 1. Change the value of default expiration time.
-1. Hit **Save changes** for the changes to take effect.
+1. Click **Save changes** for the changes to take effect.
 
 This setting is set per job and can be overridden in
 [`.gitlab-ci.yml`](../../../ci/yaml/README.md#artifactsexpire_in).
@@ -100,9 +100,10 @@ On GitLab.com, the quota is calculated based on your
 
 To change the pipelines minutes quota:
 
-1. Go to **Admin Area > Settings > CI/CD**
-1. Set the pipeline minutes quota limit.
-1. Hit **Save changes** for the changes to take effect
+1. Go to **Admin Area > Settings > CI/CD**.
+1. Expand **Continuous Integration and Deployment**.
+1. In the **Pipeline minutes quota** box, enter the maximum number of minutes.
+1. Click **Save changes** for the changes to take effect.
 
 ---
 
@@ -111,8 +112,8 @@ also change each group's pipeline minutes quota to override the global value.
 
 1. Navigate to the **Admin Area > Overview > Groups** and hit the **Edit**
    button for the group you wish to change the pipeline minutes quota.
-1. Set the pipeline minutes quota to the desired value
-1. Hit **Save changes** for the changes to take effect.
+1. In the **Pipeline Minutes Quota** box, enter the maximum number of minutes.
+1. Click **Save changes** for the changes to take effect.
 
 Once saved, you can see the build quota in the group admin view.
 The quota can also be viewed in the project admin view if shared Runners