Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
ce7628fa
Commit
ce7628fa
authored
Feb 01, 2022
by
Ben Bodenmiller
Committed by
Suzanne Selhorn
Feb 01, 2022
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Docs: Fix dead link to autoscaler executor repo
parent
01b824b1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/ci/runners/saas/windows_saas_runner.md
doc/ci/runners/saas/windows_saas_runner.md
+1
-1
No files found.
doc/ci/runners/saas/windows_saas_runner.md
View file @
ce7628fa
...
@@ -15,7 +15,7 @@ change when the beta period ends, as discussed in this [related issue](https://g
...
@@ -15,7 +15,7 @@ change when the beta period ends, as discussed in this [related issue](https://g
Windows runners on GitLab.com autoscale by launching virtual machines on
Windows runners on GitLab.com autoscale by launching virtual machines on
the Google Cloud Platform. This solution uses an
the Google Cloud Platform. This solution uses an
[
autoscaling driver
](
https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/
tree/master/docs/readme
.md
)
[
autoscaling driver
](
https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/autoscaler/
-/blob/main/docs/README
.md
)
developed by GitLab for the
[
custom executor
](
https://docs.gitlab.com/runner/executors/custom.html
)
.
developed by GitLab for the
[
custom executor
](
https://docs.gitlab.com/runner/executors/custom.html
)
.
Windows runners execute your CI/CD jobs on
`n1-standard-2`
instances with
Windows runners execute your CI/CD jobs on
`n1-standard-2`
instances with
2 vCPUs and 7.5 GB RAM. You can find a full list of available Windows packages in
2 vCPUs and 7.5 GB RAM. You can find a full list of available Windows packages in
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment