hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: trunk vs. precommit dev env
Date Sat, 06 Apr 2013 00:03:42 GMT
Also I am remiss to mention that the JDK version used on EC2 Jenkins is
currently JDK6. I've been meaning to bring up discussion on moving to JDK7
there. It's already installed on the AMI, the only change necessary is to
the node configuration in Jenkins.


On Fri, Apr 5, 2013 at 12:22 PM, Andrew Purtell <apurtell@apache.org> wrote:

> It seems better to me to change precommit builds to jdk7 too. Otherwise
> wouldn't we be relying on a EOL product for build stability? With the flaky
> test category under discussion we can get green builds that way without
> keeping one foot (or both) in the past. Thoughts?
>
> As for moving builds to the hadoop* machines, +1 they seem cleaner.
>
>
> On Friday, April 5, 2013, Stack wrote:
>
>> On Fri, Apr 5, 2013 at 11:36 AM, Nicolas Liochon <nkeywal@gmail.com>
>> wrote:
>>
>> >  -Dsurefire.
>> > secondPartThreadCount=2 will make it so only two // tests
>> >
>> > Yes. I think we should use jdk 1.6 as well.
>> >
>> >
>> >
>> Go for it.  We had a jdk7 discussion a while back and switched trunk build
>> to jdk7 as a result.  Stability is more important so feel free to change
>> if
>> that will help improve it.
>>
>>
>> > You don't want to run the trunk on hadoop* machines? This would be safer
>> > imho.
>> >
>> >
>> Go for it.
>>
>> St.Ack
>>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message