From 06b2557bd1c44098206ba4f39a9c19db9670a896 Mon Sep 17 00:00:00 2001
From: Stan Hu <stanhu@gmail.com>
Date: Wed, 11 Dec 2019 06:23:52 -0800
Subject: [PATCH] Set GIT_DEPTH to 20

Before if the SHA of the last CI run were ahead of the next CI run by
more than 50 commits, the build would fail because Git assumes the full
history is present
(https://gitlab.com/gitlab-org/gitlab/issues/33041). It does not know
the current repository has a shallow clone.

With https://gitlab.com/gitlab-org/gitlab/issues/39134, the pre-clone
script now seeds the repository with the full history of `master` and a
consistent snapshot. As a result, we should be able to use a shallow
clone with a lower depth, which should decrease the load from the
server.
---
 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 722c5043c4a3e..45d0dbf1c7c7e 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -17,7 +17,7 @@ variables:
   RAILS_ENV: "test"
   NODE_ENV: "test"
   SIMPLECOV: "true"
-  GIT_DEPTH: "50"
+  GIT_DEPTH: "20"
   GIT_SUBMODULE_STRATEGY: "none"
   GET_SOURCES_ATTEMPTS: "3"
   KNAPSACK_RSPEC_SUITE_REPORT_PATH: knapsack/report-master.json
-- 
GitLab