Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of nkeywal@gmail.com designates
 209.85.212.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADcMMgERM4nsar-K4uJiPG8m2GEVMOjhReHEHz8L18qGMZWUvA@mail.gmail.com>
References: 
 <CAAha9a1dgA8UTVyDC8g3k7k2Oyx+yL21RQD-p-BmrkQ51YAi4w@mail.gmail.com>
 <CADcMMgERM4nsar-K4uJiPG8m2GEVMOjhReHEHz8L18qGMZWUvA@mail.gmail.com>
From: Nicolas Liochon <nkeywal@gmail.com>
Date: Fri, 26 Apr 2013 06:09:59 +0200
Message-ID: 
 <CAPcDmSvQ=Gq_5Ei5Zx6ksaQP522vkL0w=T94BverUqdtWS35Zg@mail.gmail.com>
Subject: Re: [DISCUSS] Making hadoop 2 the default precommit for trunk ones we
 get green builds
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7bb04d7e90273904db3bb6a7

--047d7bb04d7e90273904db3bb6a7
Content-Type: text/plain; charset=ISO-8859-1

+1 as well.


On Fri, Apr 26, 2013 at 5:55 AM, Stack <stack@duboce.net> wrote:

> +1 on this idea.
>
>
> On Thu, Apr 25, 2013 at 5:34 PM, Jonathan Hsieh <jon@cloudera.com> wrote:
>
> > tl;dr after we get hadoop2 build fixed, how about making hadoop2 the
> > default for trunk precommit and trunk jenkins jobs?
> >
> > Over in HBASE-6891, we've fixed the unit tests with hadoop2 on trunk that
> > always fail or always hang.  We are getting close on getting the hadoop2
> +
> > trunk build passing (right now there are a combination of tests that hang
> > sometimes or fail sometimes -- and I've seen a run where the hbase-server
> > module passed on hadoop2).
> >
> > Initially I was thinking that we'd create a two-headed precommit script
> > that ran unit tests against trunk on hadoop1 and hadoop2.  This was far
> > down in a thread so may not have been considered by many folks.   I'd
> like
> > to suggest (actually Elliot's idea) that we set the default precommit
> trunk
> > build to be against hadoop2.  Over the "normal" jenkins runs, we'd move
> > trunk to hadoop2 as well.  We would however keep the 0.95 branch against
> > hadoop 1.x and would thus get coverage of much of the new code under both
> > setups.
> >
> > This buys us two things:
> >
> > 1) We get coverage against hadoop2, which will likely be the post
> > singularity hbase should use as a default.
> > 2) We end up having the same number of build jobs and avoid having two
> > separate hadoop2 hadoop1 precommit builds for trunk.
> >
> > Thoughts?
> >
> > Jon
> >
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // jon@cloudera.com
> >
>

--047d7bb04d7e90273904db3bb6a7--