The recent patch to enable shallow cloning added a method to skip
it by checking if GIT_DEPTH was null. However, this could never
be triggered because if the user specified it as null, the default
setting code would take over and set it to 1.
This patch allows the user to specify GIT_DEPTH=0 to skip the
shallow clone.
Change-Id: I00ea7ab54ed51dc3ede9ceb9ff0f11575a035d1c
... | ... |
@@ -697,7 +697,8 @@ SYSLOG_PORT=${SYSLOG_PORT:-516} |
697 | 697 |
LOG_COLOR=$(trueorfalse True LOG_COLOR) |
698 | 698 |
|
699 | 699 |
# Set global ``GIT_DEPTH=<number>`` to limit the history depth of the git clone |
700 |
-GIT_DEPTH=${GIT_DEPTH:-1} |
|
700 |
+# Set to 0 to disable shallow cloning |
|
701 |
+GIT_DEPTH=${GIT_DEPTH:-0} |
|
701 | 702 |
|
702 | 703 |
# Use native SSL for servers in SSL_ENABLED_SERVICES |
703 | 704 |
USE_SSL=$(trueorfalse False USE_SSL) |