diff options
Diffstat (limited to 'doc/ci/runners/saas')
| -rw-r--r-- | doc/ci/runners/saas/linux_saas_runner.md | 2 | ||||
| -rw-r--r-- | doc/ci/runners/saas/macos/codesigning.md | 11 | ||||
| -rw-r--r-- | doc/ci/runners/saas/macos/environment.md | 11 | ||||
| -rw-r--r-- | doc/ci/runners/saas/macos_saas_runner.md | 34 | ||||
| -rw-r--r-- | doc/ci/runners/saas/windows_saas_runner.md | 21 |
5 files changed, 29 insertions, 50 deletions
diff --git a/doc/ci/runners/saas/linux_saas_runner.md b/doc/ci/runners/saas/linux_saas_runner.md index dd5381f3cd6..c026ccf3d22 100644 --- a/doc/ci/runners/saas/linux_saas_runner.md +++ b/doc/ci/runners/saas/linux_saas_runner.md @@ -29,7 +29,7 @@ The `small` machine type is set as default. If no [tag](../../yaml/index.md#tags the jobs will run on this default runner. All SaaS runners on Linux currently run on -[`n2d-standard`](https://cloud.google.com/compute/docs/general-purpose-machines#n2d_machines) gerneral-purpose compute from GCP. +[`n2d-standard`](https://cloud.google.com/compute/docs/general-purpose-machines#n2d_machines) general-purpose compute from GCP. The machine type and underlying processor type can change. Jobs optimized for a specific processor design could behave inconsistently. ## Container images diff --git a/doc/ci/runners/saas/macos/codesigning.md b/doc/ci/runners/saas/macos/codesigning.md deleted file mode 100644 index 7e70e984c7c..00000000000 --- a/doc/ci/runners/saas/macos/codesigning.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -redirect_to: '../macos_saas_runner.md' -remove_date: '2023-09-05' ---- - -This document was moved to [another location](../macos_saas_runner.md). - -<!-- This redirect file can be deleted after <2023-09-05>. --> -<!-- Redirects that point to other docs in the same project expire in three months. --> -<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. --> -<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
\ No newline at end of file diff --git a/doc/ci/runners/saas/macos/environment.md b/doc/ci/runners/saas/macos/environment.md deleted file mode 100644 index 7e70e984c7c..00000000000 --- a/doc/ci/runners/saas/macos/environment.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -redirect_to: '../macos_saas_runner.md' -remove_date: '2023-09-05' ---- - -This document was moved to [another location](../macos_saas_runner.md). - -<!-- This redirect file can be deleted after <2023-09-05>. --> -<!-- Redirects that point to other docs in the same project expire in three months. --> -<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. --> -<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->
\ No newline at end of file diff --git a/doc/ci/runners/saas/macos_saas_runner.md b/doc/ci/runners/saas/macos_saas_runner.md index 44f99ed6ccc..1445ae58bd4 100644 --- a/doc/ci/runners/saas/macos_saas_runner.md +++ b/doc/ci/runners/saas/macos_saas_runner.md @@ -4,7 +4,7 @@ group: Runner info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# SaaS runners on macOS (Beta) **(PREMIUM SAAS)** +# SaaS runners on macOS **(PREMIUM SAAS BETA)** SaaS runners on macOS are in [Beta](../../../policy/experiment-beta-support.md#beta) for open source programs and customers in Premium and Ultimate plans. @@ -38,28 +38,30 @@ in your `.gitlab-ci.yml` file. Each image runs a specific version of macOS and Xcode. -| VM image | Status | -|---------------------------|---------------| -| `macos-12-xcode-13` | `maintenance` | -| `macos-12-xcode-14` | `maintenance` | -| (none, awaiting macOS 13) | `beta` | +| VM image | Status | +|----------------------------|--------| +| `macos-12-xcode-13` | `GA` | +| `macos-12-xcode-14` | `GA` | +| `macos-13-xcode-14` | `Beta` | -NOTE: -If your job requires tooling or dependencies not available in our available images, those can only be installed in the job execution. +## Image update policy for macOS -## Image update policy +macOS and Xcode follow a yearly release cadence, during which GitLab increments its versions synchronously. GitLab typically supports multiple versions of preinstalled tools. For more information, see +a [full list of preinstalled software](https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/job-images/-/tree/main/toolchain). -GitLab expects to release new images based on this cadence: +GitLab provides `stable` and `latest` macOS images that follow different update patterns: -macOS updates: +- **Stable image:** The `stable` images and installed components are updated every release. Images without the `:latest` prefix are considered stable images. +- **Latest image:** The `latest` images are typically updated on a weekly cadence and use a `:latest` prefix in the image name. Using the `latest` image results in more regularly updated components and shorter update times for Homebrew or asdf. The `latest` images are used to test software components before releasing the components to the `stable` images. +By definition, the `latest` images are always Beta. +A `latest` image is not available. -- **For new OS versions:** When Apple releases a new macOS version to developers (like macOS `12`), GitLab will plan to release an image based on the OS within the next 30 business days. The image is considered `beta` and the contents of the image (including tool versions) are subject to change until the first patch release (`12.1`). The long-term name will not include `beta` (for example, `macos-12-xcode-13`), so customers are moved automatically out of beta over time. GitLab will try to minimize breaking changes between the first two minor versions but makes no guarantees. Tooling often gets critical bug fixes after the first public release of an OS version. +### Image release process -- **After the first patch release (`12.1`):** - - The image moves to `maintenance` mode. The tools GitLab builds into the image with Homebrew and asdf are frozen. GitLab continues making Xcode updates, security updates, and any non-breaking changes deemed necessary. - - The image for the previous OS version (`11`) moves to `frozen` mode. GitLab then does only unavoidable changes: security updates, runner version upgrades, and setting the production password. +When Apple releases a new macOS version, GitLab releases both `stable` and `latest` images based on the OS in the next release. Both images are Beta. -Both macOS and Xcode follow a yearly release cadence. As time goes on, GitLab increments their versions synchronously (meaning we build macOS 11 with Xcode 12, macOS 12 with Xcode 13, and so on). +With the release of the first patch to macOS, the `stable` image becomes Generally Available (GA). +As only two GA images are supported at a time, the prior OS version becomes deprecated and is deleted after three months in accordance with the [supported image lifecycle](../index.md#supported-image-lifecycle). ## Example `.gitlab-ci.yml` file diff --git a/doc/ci/runners/saas/windows_saas_runner.md b/doc/ci/runners/saas/windows_saas_runner.md index 8ec44b8c275..108388f22c8 100644 --- a/doc/ci/runners/saas/windows_saas_runner.md +++ b/doc/ci/runners/saas/windows_saas_runner.md @@ -4,7 +4,7 @@ group: Runner info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# SaaS runners on Windows (Beta) **(FREE SAAS)** +# SaaS runners on Windows **(FREE SAAS BETA)** SaaS runner on Windows autoscale by launching virtual machines on the Google Cloud Platform. This solution uses an @@ -35,7 +35,7 @@ You can execute your job in one of the following Windows versions: | Version tag | Status | |----------------|---------------| -| `windows-1809` | `maintenance` | +| `windows-1809` | `Beta` | You can find a full list of available pre-installed software in the [pre-installed software documentation](https://gitlab.com/gitlab-org/ci-cd/shared-runners/images/gcp/windows-containers/blob/main/cookbooks/preinstalled-software/README.md). @@ -81,16 +81,15 @@ test: - echo "running scripts in the test job" ``` -## Limitations and known issues +## Known issues -- All the limitations mentioned in our [Beta definition](../../../policy/experiment-beta-support.md#beta). -- The average provisioning time for a new Windows VM is 5 minutes. - This means that you may notice slower build start times - on the Windows runner fleet during the beta. In a future - release we intend to update the autoscaler to enable - the pre-provisioning of virtual machines. This is intended to significantly reduce - the time it takes to provision a VM on the Windows fleet. You can - follow along in the [related issue](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/-/issues/32). +- For more information about support for Beta features, see [Beta](../../../policy/experiment-beta-support.md#beta). +- The average provisioning time for a new Windows virtual machine (VM) is five minutes, so + you might notice slower start times for builds on the Windows runner + fleet during the Beta. Updating the autoscaler to enable the pre-provisioning + of virtual machines is proposed in a future release. This update is intended to + significantly reduce the time it takes to provision a VM on the Windows fleet. + For more information, see [issue 32](https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/-/issues/32). - The Windows runner fleet may be unavailable occasionally for maintenance or updates. - The job may stay in a pending state for longer than the |