diff options
| -rw-r--r-- | docs/developer_info/Building_SO.rst | 2 | ||||
| -rw-r--r-- | docs/developer_info/FAQs.rst | 2 | ||||
| -rw-r--r-- | docs/release-notes.rst | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/docs/developer_info/Building_SO.rst b/docs/developer_info/Building_SO.rst index 7d68e433cc..edd2515fee 100644 --- a/docs/developer_info/Building_SO.rst +++ b/docs/developer_info/Building_SO.rst @@ -36,7 +36,7 @@ Build docker images 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. diff --git a/docs/developer_info/FAQs.rst b/docs/developer_info/FAQs.rst index cd6784071c..55a7049f49 100644 --- a/docs/developer_info/FAQs.rst +++ b/docs/developer_info/FAQs.rst @@ -57,7 +57,7 @@ How to Build docker images 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. diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 4fb098f656..ed8c7de674 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -439,7 +439,7 @@ The main goal of the El-Alto release was to improve documentation, UT improvemen - [`SO-2354 <https://jira.onap.org/browse/SO-2354>`__\ ] - vCPE model_customization_id not found on create vfmodule - [`SO-2351 <https://jira.onap.org/browse/SO-2351>`__\ ] - SO Distribution Error on Allotted Resource - duplicate primary - [`SO-2349 <https://jira.onap.org/browse/SO-2349>`__\ ] - Exception in DMAAP Client when PNF_READY event arrives from PRH -- [`SO-2337 <https://jira.onap.org/browse/SO-2337>`__\ ] - Git clone not working for CSIT filename too long +- [`SO-2337 <https://jira.onap.org/browse/SO-2337>`__\ ] - git clone --depth 1 not working for CSIT filename too long - [`SO-2289 <https://jira.onap.org/browse/SO-2289>`__\ ] - CreateVcpeResCustService_simplified workflow used in PnP PNF registration workflow returns an exception in Dmaap listener - [`SO-2229 <https://jira.onap.org/browse/SO-2229>`__\ ] - sdc adapter and openstack container in crash loopback - [`SO-2228 <https://jira.onap.org/browse/SO-2228>`__\ ] - SDC Handler crash loopback |