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
Sounds like a nice plan.
On Apr 6, 2013, at 4:38 AM, Nicolas Liochon 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 woul
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
-
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 P
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
On Fri, Apr 5, 2013 at 11:36 AM, Nicolas Liochon 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 mo
-Dsurefire.
secondPartThreadCount=2 will make it so only two // tests
Yes. I think we should use jdk 1.6 as well.
You don't want to run the trunk on hadoop* machines? This would be safer
imho.
I'm leaving now, but I can trigger a few builds set on hadoop & jdk 1.6
tomorrow, when the bay area w
On Fri, Apr 5, 2013 at 8:29 AM, Nicolas Liochon wrote:
> Hi,
>
> It took me ages, but I found the difference between trunk and precommit
> builds.
> Precommits are executed on hadoop* machines. There is a single build at a
> time.
> Trunks are executed on ubuntu* machines. There are two simultane
On Fri, Apr 5, 2013 at 9:43 AM, Nicolas Liochon wrote:
> Hum, I can't see the content of the url. After the authentication I have an
> unreadable page.
I added you to the jenkins admin group (I followed instructions here:
http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson#FAQ_Fo
Hum, I can't see the content of the url. After the authentication I have an
unreadable page.
You're mentionning a precommit setting, but the property I got for my last
try was with a 1.6 jdk?
On Fri, Apr 5, 2013 at 6:30 PM, Ted Yu wrote:
> On https://builds.apache.org/job/PreCommit-HBASE-Build/
On https://builds.apache.org/job/PreCommit-HBASE-Build/configure , the JDK
has been changed to 1.7 latest.
Not sure who changed that.
On Fri, Apr 5, 2013 at 9:11 AM, Nicolas Liochon wrote:
> And, from HBASE-8280, it seems we don't use the same jvm for trunk and for
> precommit builds.
>
> prec
On https://builds.apache.org/job/HBase-TRUNK/configure, you should be able
to modify 'Label Expression' which selects build machines.
bq. When building trunk, use a very low parallel test factor. May be 2.
+1 for the above suggestion.
On Fri, Apr 5, 2013 at 8:29 AM, Nicolas Liochon wrote:
> Hi
And, from HBASE-8280, it seems we don't use the same jvm for trunk and for
precommit builds.
precommit build => *1.6*
13/04/05 14:29:02 INFO util.TestShowProperties: Property
sun.boot.library.path=/home/jenkins/tools/java/jdk1.6.0_26/jre/lib/i386
13/04/05 14:29:02 INFO util.TestShowProperties: Pr
13 matches
Mail list logo
