Any luck with this? On Thu, Aug 25, 2016 at 10:47 AM, Jim Apple <jbap...@cloudera.com> wrote:
> That sounds to me like a network config issue. > > As far as what the code should be based on, the Apache repo and the gerrit > repo should be close, with apache being a few commits behind at most. I use > gerrit almost exclusively, because that way I know my patches will be based > on the most recent tree. > > On Mon, Aug 22, 2016 at 5:20 AM, Nishidha Panpaliya <nishi...@us.ibm.com> > wrote: > >> Hi Jim, >> >> We tried the steps mentioned at https://cwiki.apache.org/confl >> uence/display/IMPALA/How+to+switch+to+Apache-hosted+git. >> On Cloudera's Impala source tree -> >> $git remote add apache https://git-wip-us.apache.org/ >> repos/asf/incubator-impala.git >> $git remote add asf-gerrit ssh://npanpaliya@gerrit.cloude >> ra.org:29418/Impala-ASF >> (Here, npanpaliya is my github id which I also used for gerrit login, >> also added my ssh key to my gerrit settings) >> $git fetch asf-gerrit >> ssh: Could not resolve hostname gerrit.cloudera.org:29418: Name or >> service not known >> >> fatal: Could not read from remote repository. >> >> Please make sure you have the correct access rights >> and the repository exists. >> >> >> Could you please help us with this error? >> >> Our understanding is we need repo referred by "asf-gerrit" only for >> uploading gerrit code reviews. To work (build, modify, port, test) on >> actual Impala code base, we still have to follow the steps at >> https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala. that >> uses code base referred by "apache" remote. >> >> Thanks, >> Nishidha >> >> [image: Inactive hide details for Jim Apple ---08/19/2016 08:58:00 PM---> >> [Nishidha] We found two new source code URLs as one mentioned]Jim Apple >> ---08/19/2016 08:58:00 PM---> [Nishidha] We found two new source code URLs >> as one mentioned in Confluence > https://git-wip-us.a >> >> From: Jim Apple <jbap...@cloudera.com> >> To: Nishidha Panpaliya/Austin/Contr/IBM@IBMUS >> Cc: "dev@impala" <dev@impala.incubator.apache.org>, Manish >> Patil/Austin/Contr/IBM@IBMUS, Silvius Rus <s...@cloudera.com>, Valencia >> Serrao/Austin/Contr/IBM@IBMUS, Sudarshan Jagadale/Austin/Contr/IBM@IBMUS, >> Zhi Zhi NY Yang <zhiz...@cn.ibm.com> >> Date: 08/19/2016 08:58 PM >> Subject: Re: Contributions to Cloudera Impala >> ------------------------------ >> >> >> >> > [Nishidha] We found two new source code URLs as one mentioned in >> Confluence >> > https://git-wip-us.apache.org/repos/asf/incubator-impala.git and >> another to >> > be https://github.com/apache/incubator-impala. >> > Commits wise both look same, though former one says "wip" in the URL. >> Please >> > suggest the URL to be forked and worked upon. >> >> I don't know exactly what you mean by "forked" in this context. You >> should use the repo referred to as "asf-gerrit" in >> https://cwiki.apache.org/confluence/display/IMPALA/How+to+ >> switch+to+Apache-hosted+git >> >> > [Nishidha] Okay. So, after CLA, can we work directly on Apache's Impala >> or >> > we'll need to fork it into our repository and create a new branch from >> > master, and then generate PRs/Gerrit code reviews from it? >> >> I don't understand this question, but let me try and clarify some >> things that may help you answer it. >> >> All of Impala's commits get code reviews on gerrit. >> >> We don't use PRs. >> >> > [Nishidha] Which CI do you have or working on? >> >> Cloudera uses Jenkins. >> >> > What is the expected timeline for your CI to be publicly available? >> >> You can follow https://issues.cloudera.org/browse/IMPALA-3228 to learn >> about updates. >> >> Apache projects are sometimes referred to as "do-ocracies". If you >> would like to find a CI hosting provider that will support Apache >> Impala, you are welcome to help - you don't have to be an Impala >> committer or a CLoudera employee to help. >> >> > 1. Would you suggest me to start a new thread for branch discussion, >> > although I created a gist in github.com >> > https://gist.github.com/npanpaliya/bd58e554370455babc5c4f290e4b1723 for >> the >> > same? >> >> Yes. Apache Impala project direction discussions are unlikely to >> happen on private gists. >> >> >> >> >
