RE: Git repo ready to use

Thanks Karthik for making Git repo ready. Regards, Yi Liu -Original Message- From: Karthik Kambatla [mailto:ka...@cloudera.com] Sent: Thursday, August 28, 2014 2:26 PM To: common-dev@hadoop.apache.org Subject: Re: Git repo ready to use We just got HADOOP-11001 in. If you have access, c

Re: Git repo ready to use

We just got HADOOP-11001 in. If you have access, can you please try modifying the Jenkins jobs taking the patch on HADOOP-11001 into consideration. On Wed, Aug 27, 2014 at 4:38 PM, Ted Yu wrote: > I have access. > > I can switch the repository if you think it is time to do so. > > > On Wed, Aug

[jira] [Created] (HADOOP-11015) Http server/client utils to propagate and recreate Exceptions from server to client

Alejandro Abdelnur created HADOOP-11015: --- Summary: Http server/client utils to propagate and recreate Exceptions from server to client Key: HADOOP-11015 URL: https://issues.apache.org/jira/browse/HADOOP-1101

[jira] [Resolved] (HADOOP-10958) TestGlobPaths should do more tests of globbing by unprivileged users

[ https://issues.apache.org/jira/browse/HADOOP-10958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HADOOP-10958. --- Resolution: Duplicate I rolled this fix into HADOOP-10957 at Daryn's reques

[jira] [Created] (HADOOP-11014) Potential resource leak in JavaKeyStoreProvider due to unclosed stream

Ted Yu created HADOOP-11014: --- Summary: Potential resource leak in JavaKeyStoreProvider due to unclosed stream Key: HADOOP-11014 URL: https://issues.apache.org/jira/browse/HADOOP-11014 Project: Hadoop Common

Re: Git repo ready to use

I have access. I can switch the repository if you think it is time to do so. On Wed, Aug 27, 2014 at 4:35 PM, Karthik Kambatla wrote: > Thanks for reporting it, Ted. We are aware of it - second follow-up item in > my earlier email. > > Unfortunately, I don't have access to the builds to fix th

Re: Git repo ready to use

Thanks for reporting it, Ted. We are aware of it - second follow-up item in my earlier email. Unfortunately, I don't have access to the builds to fix them and don't quite know the procedure to get access either. I am waiting for someone with access to help us out. On Wed, Aug 27, 2014 at 3:45 PM

[jira] [Created] (HADOOP-11013) CLASSPATH handling should be considated, debuggable

Allen Wittenauer created HADOOP-11013: - Summary: CLASSPATH handling should be considated, debuggable Key: HADOOP-11013 URL: https://issues.apache.org/jira/browse/HADOOP-11013 Project: Hadoop Common

Re: Git repo ready to use

Precommit builds are still using svn : https://builds.apache.org/job/PreCommit-HDFS-Build/configure https://builds.apache.org/job/PreCommit-YARN-Build/configure FYI On Wed, Aug 27, 2014 at 7:00 AM, Ted Yu wrote: > Currently Jenkins builds still use subversion as source. > > Should Jenkins poi

Re: Updates on migration to git

Thanks for making this happen, Karthik and Daniel. Great job. best, Colin On Tue, Aug 26, 2014 at 5:59 PM, Karthik Kambatla wrote: > Yes, we have requested for force-push disabled on trunk and branch-* > branches. I didn't test it though :P, it is not writable yet. > > > On Tue, Aug 26, 2014 at

Re: Git repo ready to use

svngit2jira would write a message like this - https://issues.apache.org/jira/browse/CLOUDSTACK-1638?focusedCommentId=13714929&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13714929 with a link to the commit like this - https://git-wip-us.apache.org/repos/asf?p=clouds

Re: Git repo ready to use

It appears the comments from Hudson on our JIRAs (post commits) are not setup by the INFRA team. Do we use any other scripts for this? If yes, do we want to fix those scripts or use svngit2jira? On Wed, Aug 27, 2014 at 10:18 AM, Karthik Kambatla wrote: > The emails for commits apparently all go

Re: Git repo ready to use

The emails for commits apparently all go to common-commits@, irrespective of the project. Apparently, the git filtering is not as good as svn filtering. Daniel offered to look into alternatives this coming weekend. I filed INFRA-8250 to restore updates to JIRA on commits. On Wed, Aug 27, 2014 at

[jira] [Created] (HADOOP-11011) With crypto, no native lib systems are too verbose

Allen Wittenauer created HADOOP-11011: - Summary: With crypto, no native lib systems are too verbose Key: HADOOP-11011 URL: https://issues.apache.org/jira/browse/HADOOP-11011 Project: Hadoop Common

Re: Git repo ready to use

Currently Jenkins builds still use subversion as source. Should Jenkins point to git ? Cheers On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla wrote: > Oh.. a couple more things. > > The git commit hashes have changed and are different from what we had on > our github. This might interfere w

Re: Git repo ready to use

Sorry for the noice. :) please ignore. All is well :) I think, I did a mistake while checking out branch-2.5. used "git checkout *-b *branch-2.5" instead of "git checkout branch-2.5" Regards, Vinay On Wed, Aug 27, 2014 at 2:52 PM, Karthik Kambatla wrote: > On Wed, Aug 27, 2014 at 2:19 AM, Vi

Re: Git repo ready to use

On Wed, Aug 27, 2014 at 2:19 AM, Vinayakumar B wrote: > Hi Karthik, > > Good to see migration completed. > > Currently, *branch-2.5* points to *trunk *itself. I think it should point > to *origin/branch-2.5 *right? > Are you referring to your local branch-2.5? What is origin? branch-2.5 looks

Re: Git repo ready to use

Hi Karthik, Good to see migration completed. Currently, *branch-2.5* points to *trunk *itself. I think it should point to *origin/branch-2.5 *right? Regards, Vinay On Wed, Aug 27, 2014 at 2:10 PM, Karthik Kambatla wrote: > Oh.. a couple more things. > > The git commit hashes have changed an

Re: Git repo ready to use

Committed YARN-2035 successfully via git. Email notification seems to work already. On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla wrote: > Oh.. a couple more things. > > The git commit hashes have changed and are different from what we had on > our github. This might interfere with any buil

Build failed in Jenkins: Hadoop-Common-0.23-Build #1054

See -- [...truncated 8263 lines...] Running org.apache.hadoop.io.TestBloomMapFile Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.883 sec Running org.apache.hadoop.io.TestObject

Re: Git repo ready to use

Oh.. a couple more things. The git commit hashes have changed and are different from what we had on our github. This might interfere with any build automations that folks have. Another follow-up item: email and JIRA integration On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla wrote: > Hi fol

Git repo ready to use

Hi folks, I am very excited to let you know that the git repo is now writable. I committed a few changes (CHANGES.txt fixes and branching for 2.5.1) and everything looks good. Current status: 1. All branches have the same names, including trunk. 2. Force push is disabled on trunk, branch-2