[jira] [Resolved] (MAPREDUCE-3839) Improve the single node setup docs for MR

2014-01-30 Thread Akira AJISAKA (JIRA)
[ https://issues.apache.org/jira/browse/MAPREDUCE-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved MAPREDUCE-3839. -- Resolution: Duplicate Closing this issue. > Improve the single node setup docs for

Re: Apache jenkins job to build release artifacts (WAS: Issue with my username on my company provided dev box?)

2014-01-30 Thread Roman Shaposhnik
On Thu, Jan 30, 2014 at 5:05 PM, Alejandro Abdelnur wrote: > I agree on not auto-signing (the script does not do it, on purpose). > > I was referring to deploying release artifact JARs. Right. And my answer then would be -- please don't do that. > OK, then we are done then. Sounds like it. Tha

Re: Apache jenkins job to build release artifacts (WAS: Issue with my username on my company provided dev box?)

2014-01-30 Thread Alejandro Abdelnur
I agree on not auto-signing (the script does not do it, on purpose). I was referring to deploying release artifact JARs. OK, then we are done then. Thanks. On Thu, Jan 30, 2014 at 5:02 PM, Roman Shaposhnik wrote: > On Thu, Jan 30, 2014 at 4:43 PM, Alejandro Abdelnur > wrote: > > We could

Re: Apache jenkins job to build release artifacts (WAS: Issue with my username on my company provided dev box?)

2014-01-30 Thread Roman Shaposhnik
On Thu, Jan 30, 2014 at 4:43 PM, Alejandro Abdelnur wrote: > We could improve this script further to deploy the built JARs to the Maven > repo. I don't know how to do this, so it would be great if somebody that > know how jumps on that. Maybe a s a follow up JIRA, so we have something > going. If

Apache jenkins job to build release artifacts (WAS: Issue with my username on my company provided dev box?)

2014-01-30 Thread Alejandro Abdelnur
[Cross-posting with https://issues.apache.org/jira/browse/HADOOP-10313] OK, we have: * A script, create-release.sh, that creates release artifacts * An Apache Jenkins job that runs the script and produces the artifacts in Apache CI machines, thanks Yahoo! (or shouldn't I say that?) The Apache Je

Re: Re-swizzle 2.3

2014-01-30 Thread Vinod Kumar Vavilapalli
That was quite some exercise, but I'm done with it now. Updated YARN's and MAPREDUCE's CHANGES.txt on trunk, branch-2 and branch-2.3. Let me know if you find some inaccuracies. Thanks, +Vinod On Jan 29, 2014, at 10:49 PM, Vinod Kumar Vavilapalli wrote: > > Okay, I'll look at YARN and MR CHA

Re: Re-swizzle 2.3

2014-01-30 Thread Aaron T. Myers
I just committed HADOOP-10310 to branch-2.3, so we're good to go there. (Thanks to Andrew and Daryn for the prompt reviews.) -- Aaron T. Myers Software Engineer, Cloudera On Wed, Jan 29, 2014 at 6:52 PM, Aaron T. Myers wrote: > I just filed this JIRA as a blocker for 2.3: > https://issues.apac

Hadoop-Mapreduce-trunk - Build # 1683 - Still Failing

2014-01-30 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1683/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 34483 lines...] Tests run: 7, Failures: 0, Errors: 0