Skip to content

GIT_SUBMODULE_STRATEGY to none

Summary

I believe that whenever GIT_STRATEGY is set to None, GIT_SUBMODULE_STRATEGY should be set to None for the specific job too...

Steps to reproduce

Set global variable GIT_SUBMODULE_STRATEGY: recursive

Create a job with local variable GIT_STRATEGY: none

Job will fail as the submodule updating will fail as no git repo is available

Actual behavior

Runner tries to update recursive the submodules while no git repo available

Expected behavior

GIT_SUBMODULE_STRATEGY should be set to none

Relevant logs and/or screenshots

Running with gitlab-ci-multi-runner 1.10.4 (b32125f)
Using Docker executor with image debian:latest ...
Pulling docker image debian:latest ...
Running on runner-e22cd6fc-project-1858-concurrent-0 via xxxx...
Skipping Git repository setup
Updating/initializing submodules recursively...
fatal: Not a git repository (or any of the parent directories): .git
ERROR: Build failed: exit code 1

Environment description

Private Gitlab instance

Used GitLab Runner version

Running with gitlab-ci-multi-runner 1.10.4 (b32125f)
Using Docker executor with image debian:latest ...