Verified working for https as well - I cloned just now
Also the CD server runs on master every hour - it clones using anonymous http 
via git clone http://gerrit.onap.org/r/oom
You can verify master branch (soon to be R1 branch) OOM status here until the 
job is migrated to Jenkins.onap.org

http://jenkins.onap.info/job/oom-cd/

/michael

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of LOTT, CHRISTOPHER M 
(CHRISTOPHER)
Sent: Wednesday, November 22, 2017 11:42
To: Kiruthiga R <[email protected]>
Cc: [email protected]
Subject: Re: [onap-discuss] OOM Gerrit repository page not found

This works for me (please note "https"):

   git clone https://gerrit.onap.org/r/oom


> On Nov 22, 2017, at 5:32 AM, Kiruthiga R <[email protected]> wrote:
> 
> Hi All,
>  
> As part of ONAP on Kubernetes installation, while trying to clone the oom 
> repo using anonymous http method (git clone http://gerrit.onap.org/r/oom) we 
> get page not found error.
>  
> Before Amsterdam release, git clone to oom repo was happening fine without 
> any issues. Please help.
>  
> Thanks & Regards,
> Kiruthiga
>  
> _______________________________________________
> onap-discuss mailing list
> [email protected]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IZdJcfOS7YWo6UY200A3VVFzja_rCk3u0gLN62mqPOk&m=4PZe-DacC_uJShSWH6iDiXHaefzlX6LqwAtWZU4k-co&s=vfWiHOVGA3B7RKusNt3qstSvfkDkB_paChi4m0uxJdU&e=

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to