Commit 38dbdc4a authored by Kerri Miller's avatar Kerri Miller

Merge branch 'mkarampalas-master-patch-17047' into 'master'

Fix duplicate text in What's New

See merge request gitlab-org/gitlab!54945
parents 495ac25a 6995d29d
...@@ -13,9 +13,7 @@ ...@@ -13,9 +13,7 @@
release: 13.9 release: 13.9
- title: "GPU and smart scheduling support for GitLab Runner" - title: "GPU and smart scheduling support for GitLab Runner"
body: | body: |
Previously, if you wanted to reuse the same configuration in multiple jobs, you had two options: add YAML anchors, which don't work across different configuration files, or use `extends` to reuse an entire section. Specialized compute workloads like those used in machine learning can significantly benefit from access to GPUs. Developers can configure GitLab Runner to leverage GPUs in the Docker executor by forwarding the `--gpu` flag. You can also use this with recent support in [GitLab’s fork of Docker Machine](https://docs.gitlab.com/runner/executors/docker_machine.html#using-the-forked-version-of-docker-machine), which allows you to [accelerate workloads with attached GPUs](https://cloud.google.com/compute/docs/gpus/create-vm-with-gpus). Doing so can help control costs associated with potentially expensive machine configurations.
In this release, we've added a new YAML function called `!reference`, which lets you target the exact configuration you want to reuse as part of your CI/CD pipeline, even if it's in another file.
stage: Verify stage: Verify
self-managed: true self-managed: true
gitlab-com: true gitlab-com: true
......
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