Docs feedback: Store custom clone options in config.toml
https://docs.gitlab.com/ee/ci/large_repositories/#store-custom-clone-options-in-configtoml
Hi there, I tried to define a GIT_DEPTH=1 in the config.toml configuration at the runner level.
Unfortunately this did not change anything when executing my pipeline.
Still got the default: Fetching changes with git depth set to 20...
This seems to be broken or wrongly documented.
I tried to overwrite this value from the .gitlab-ci.yml:
variables:
19
GIT_DEPTH: 3
This resulted on an awaited: Fetching changes with git depth set to 3...
in the ci logs.
I suspected that the global configuration of the project CI/CD (-/settings/ci_cd) -> General pipelines
Is superseding any gitlab-runner config.toml environment definition.
Blanking this parameter in the UI, resulted in a different log message: Fetching changes...
in the ci/cd outputs. Without any indication of the GIT_DEPTH
I am wondering how to ensure the runner defined environment shall have prevalence on the project setting if defaults in use.
Currently there is no way to enforce a runner wide GIT_DEPTH...