You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor!: group variables for better overview (#810)
Groups variables into objects to
- reduce the number of variables (currently 118)
- to gain a better overview of all configuration settings
Creates new groups of variables:
- `runner_manager` in case it configures the "main" process which sets
the defaults for all runners
- `runner` in case it configures the runner created by the runner
manager
- `runner_worker` in case it configures the docker/docker+machine or
leave it as it is, if it is a global scope, e.g. common tags, the
environment, ...
Yes and a script is provided to do that. It covers 98% of all migrations
(see migrations/migrate-to-7-0-0.sh)
Please mention the examples you have verified.
---------
Co-authored-by: Tyrone Meijn <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+4-5
Original file line number
Diff line number
Diff line change
@@ -386,13 +386,12 @@ module "runner" {
386
386
387
387
Since spot instances can be taken over by AWS depending on the instance type and AZ you are using, you may want multiple instances
388
388
types in multiple AZs. This is where spot fleets come in, when there is no capacity on one instance type and one AZ, AWS will take
389
-
the next instance type and so on. This update has been possible since the[fork](https://gitlab.com/cki-project/docker-machine/-/tree/v0.16.2-gitlab.19-cki.2)
390
-
of docker-machine supports spot fleets.
389
+
the next instance type and so on. This update has been possible since the
# Uncomment the HCL code below to configure a docker service so that registry mirror is used in auto-devops jobs
121
126
# See https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27171 and https://docs.gitlab.com/ee/ci/docker/using_docker_build.html#the-service-in-the-gitlab-runner-configuration-file
122
127
# You can check this works with a CI job like:
@@ -141,7 +146,7 @@ module "runner" {
141
146
#
142
147
# If not using an official docker image for your job, you may need to specify `DOCKER_HOST: tcp://docker:2375`
0 commit comments