OK, thanks for the update. I could see the current current build is success. https://jenkins.onap.org/job/doc-master-verify-rtd/2213/
Thanks and Regards, M Seshu Kumar Senior System Architect uTraffic, Software BU, Huawei Technologies India Pvt. Ltd. Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield Bengaluru-560066, Karnataka. Tel: + 91-80-49160700 , Mob: 9845355488 ___________________________________________________________________________________________________ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ------------------------------------------------------------------------------------------------------------------------------------------------------------------- ________________________________________ From: BENNETT, RICH via RT [onap-helpd...@rt.linuxfoundation.org] Sent: Thursday, May 24, 2018 1:10 PM To: Seshu m Cc: gg2...@att.com; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] [ONAP Helpdesk #56363] [linuxfoundation.org #56363] RE: Issue with the Doc verify build time out Seshu, We are proceeding with option 1, increase the submodule clone timeout. Patch https://gerrit.onap.org/r/#/c/48851/ is pending review. Neither the scm-repo-depth or scm-git-shallow-clone apply to submodules, but we will continue to investigate if there is jjb support for submodule shallow clones to reduce the size (from 700MB to 3MB) and time to clone the large repository. Thank you Rich _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
