Issue-ID: SO-2966 optimization in git clone using --depth
optimize the git clone using --depth flag in term of size of clone
and also in term's of time taken to fetch the files and commit history
of whole repository.
Respective issue is created at https://jira.onap.org/browse/SO-2966
More detail can be found at blog
https://www.atlassian.com/git/tutorials/big-repositories
Signed-off-by: Pratik Raj <rajpratik71@gmail.com>
Change-Id: I82d8e20a0f33e950f6a66b9f197722cdcaf182d8
diff --git a/docs/developer_info/Building_SO.rst b/docs/developer_info/Building_SO.rst
index 7d68e43..edd2515 100644
--- a/docs/developer_info/Building_SO.rst
+++ b/docs/developer_info/Building_SO.rst
@@ -36,7 +36,7 @@
SO docker images are built using the "docker" maven profile.
-During the build, the chef-repo and so-docker repositories are cloned from gerrit into the "so" directory structure. Extra definitions are required in the build environment to make this happen. You may need to adjust the definition of mso.chef.git.url.prefix to match the way you authenticate yourself when performing git clone.
+During the build, the chef-repo and so-docker repositories are cloned from gerrit into the "so" directory structure. Extra definitions are required in the build environment to make this happen. You may need to adjust the definition of mso.chef.git.url.prefix to match the way you authenticate yourself when performing git clone --depth 1.
If you are behind a corporate firewall, you can specify proxy definitions for the constructed docker images.