Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> trunk vs. precommit dev env


Copy link to this message
-
Re: trunk vs. precommit dev env
The jenkins settings on hadoop* are overwritten by the
${WORKSPACE}/nightly/hudsonEnv.sh
So whatever jdk settings you put in jenkins, you have a 1.6 at the end.

As well, the maven and jdk directory differ between the ubuntu and the
hadoop machines.

Today, for trunk and trunk on hadoop 2, I've set jdk=1.6 & parallel=2

On Sat, Apr 6, 2013 at 2:33 PM, Ted <[EMAIL PROTECTED]> wrote:

> Sounds like a nice plan.
>
> On Apr 6, 2013, at 4:38 AM, Nicolas Liochon <[EMAIL PROTECTED]> wrote:
>
> > Jenkins has been down for 15 hours now, so I can't change the
> > configuration...
> > If nobody objects, I will:
> > - set all the builds to hadoop* and jdk 1.6
> > - in parallel do a few tries on jdk 1.7. Especially, I would like to
> > ensure that we have a recent 64 bits version of the jdk1.7 on all
> machines
> > - see what's flaky with 1.6 (I think Jeffrey's tool will allow us to get
> > this list after a few days of commit)
> > - then set all the trunk builds to 1.7
> >
> >
> >
> >
> > On Sat, Apr 6, 2013 at 2:03 AM, Andrew Purtell <[EMAIL PROTECTED]>
> wrote:
> >
> >> 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 <[EMAIL PROTECTED]>
> >> 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 <[EMAIL PROTECTED]>
> >>>> 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)
> >>
>