Commit ce527675 authored by Darren Eastman's avatar Darren Eastman Committed by Marcel Amirault

Change description of minutes quota

Resolve discussion in issue 198013.
- Reworded section describing usage quotas.
parent 8b3c1eff
...@@ -198,11 +198,11 @@ The Windows Shared Runners are currently in ...@@ -198,11 +198,11 @@ The Windows Shared Runners are currently in
[beta](https://about.gitlab.com/handbook/product/#beta) and should not be used [beta](https://about.gitlab.com/handbook/product/#beta) and should not be used
for production workloads. for production workloads.
During the beta period for groups and private projects the use of During the beta period, the
Windows Shared Runners will count towards the [shared runner pipeline [shared runner pipeline quota](../admin_area/settings/continuous_integration.md#shared-runners-pipeline-minutes-quota-starter-only)
quota](https://docs.gitlab.com/ee/user/admin_area/settings/continuous_integration.html#shared-runners-pipeline-minutes-quota-starter-only) will apply for groups and projects in the same way as Linux Runners.
as if they are Linux Runners, we do have plans to change this in This may change when the beta period ends, as discussed in this
[#30835](https://gitlab.com/gitlab-org/gitlab/issues/30834). [related issue](https://gitlab.com/gitlab-org/gitlab/issues/30834).
Windows Shared Runners on GitLab.com automatically autoscale by Windows Shared Runners on GitLab.com automatically autoscale by
launching virtual machines on the Google Cloud Platform. This solution uses launching virtual machines on the Google Cloud Platform. This solution uses
...@@ -321,18 +321,17 @@ test: ...@@ -321,18 +321,17 @@ test:
- All the limitations mentioned in our [beta - All the limitations mentioned in our [beta
definition](https://about.gitlab.com/handbook/product/#beta). definition](https://about.gitlab.com/handbook/product/#beta).
- The average provisioning time for a new Windows VM is 5 minutes. - The average provisioning time for a new Windows VM is 5 minutes.
This means that for the beta you will notice slower build start times This means that you may notice slower build start times
on the Windows Shared Runner fleet compared to Linux. In a future on the Windows Shared Runner fleet during the beta. In a future
release we will add the ability to the autoscaler which will enable release we will update the autoscaler to enable
the pre-warming of virtual machines. This will significantly reduce the pre-provisioning of virtual machines. This will significantly reduce
the time it takes to provision a VM on the Windows fleet. You can the time it takes to provision a VM on the Windows fleet. You can
follow along in this follow along in the [related issue](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/issues/32).
[issue](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/issues/32).
- The Windows Shared Runner fleet may be unavailable occasionally - The Windows Shared Runner fleet may be unavailable occasionally
for maintenance or updates. for maintenance or updates.
- The Windows Shared Runner virtual machine instances do not use the - The Windows Shared Runner virtual machine instances do not use the
GitLab Docker executor. This means that unlike the Linux Shared GitLab Docker executor. This means that you will not be able to specify
Runners, you will not be able to specify `image` and `services` in [`image`](../../ci/yaml/README.md#image) or [`services`](../../ci/yaml/README.md#services) in
your pipeline configuration. your pipeline configuration.
- For the beta release, we have included a set of software packages in - For the beta release, we have included a set of software packages in
the base VM image. If your CI job requires additional software that's the base VM image. If your CI job requires additional software that's
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment