summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Pickering <matthewtpickering@gmail.com>2022-08-29 13:43:56 +0100
committerMatthew Pickering <matthewtpickering@gmail.com>2022-08-29 14:07:23 +0100
commite3678d47079559e17f082b618a6ea12f521b64fc (patch)
treedff633f18d1c48a32403de07a5bb5f5e0dbd4527
parentcbe51ac5e0bbe2667b6c7204ae62a534a9bc7c95 (diff)
downloadhaskell-wip/T22121.tar.gz
ci: Attempt using normal submodule cloning strategywip/T22121
We do not use any recursively cloned submodules, and this protects us from flaky upstream remotes. Fixes #22121
-rw-r--r--.gitlab-ci.yml2
-rwxr-xr-x.gitlab/ci.sh4
2 files changed, 3 insertions, 3 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 6ed24d600b..9e5db3bb83 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -17,7 +17,7 @@ variables:
# Overridden by individual jobs
CONFIGURE_ARGS: ""
- GIT_SUBMODULE_STRATEGY: "recursive"
+ GIT_SUBMODULE_STRATEGY: "normal"
# Makes ci.sh isolate CABAL_DIR
HERMETIC: "YES"
diff --git a/.gitlab/ci.sh b/.gitlab/ci.sh
index 906a9ffc81..1a15ea3eb4 100755
--- a/.gitlab/ci.sh
+++ b/.gitlab/ci.sh
@@ -377,8 +377,8 @@ function cleanup_submodules() {
# On Windows submodules can inexplicably get into funky states where git
# believes that the submodule is initialized yet its associated repository
# is not valid. Avoid failing in this case with the following insanity.
- git submodule sync --recursive || git submodule deinit --force --all
- git submodule update --init --recursive
+ git submodule sync || git submodule deinit --force --all
+ git submodule update --init
git submodule foreach git clean -xdf
else
info "Not cleaning submodules, not in a git repo"