Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 314A1114AA for ; Mon, 30 Jun 2014 22:27:25 +0000 (UTC) Received: (qmail 69062 invoked by uid 500); 30 Jun 2014 22:27:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 69012 invoked by uid 500); 30 Jun 2014 22:27:24 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 68995 invoked by uid 99); 30 Jun 2014 22:27:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jun 2014 22:27:24 +0000 Date: Mon, 30 Jun 2014 22:27:24 +0000 (UTC) From: "Enis Soztutar (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11441) [hadoopqa] jenkinsEnv paths are stale/wrong; JAVA_HOME in particular MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048251#comment-14048251 ] Enis Soztutar commented on HBASE-11441: --------------------------------------- I see. It seems that precommit builds are working now with jdk7-u51. keep this setup, and move on? > [hadoopqa] jenkinsEnv paths are stale/wrong; JAVA_HOME in particular > -------------------------------------------------------------------- > > Key: HBASE-11441 > URL: https://issues.apache.org/jira/browse/HBASE-11441 > Project: HBase > Issue Type: Bug > Components: build > Reporter: stack > Priority: Minor > > jenkinsEnv paths are off. > We moved to jdk1.7 for master branch. Though we'd set hadoopqa to run with java 1.7, the jenkinsEnv overrides what jenkins sets for JAVA_HOME so we've been running 1.6 java over this last couple of months rather than 1.7. > Trying to work around jenkinsEnv settings reveals that there is no 1.7 at the location jenkins goes to find it at ("Latest JDK 7" option): > {code} > ls: cannot access /home/hudson/tools/java/latest1.7/..: No such file or directory > {code} > Messing w/ the options in the jenkins UI and then putting script in text box to expose paths, almost none of the advertised options are available. > Something changed. > I got a 1.7 working by setting jdk7-u51 explicitly and then setting PATH and JAVA_HOME just before our test script runs (it downloaded it) > {code} > ... > ls $JAVA_HOME/.. > which java > java -version > echo $JAVA_HOME > saveJavaHome=$JAVA_HOME > $JAVA_HOME/bin/java -version > ulimit -a > set +x > source ${WORKSPACE}/dev-support/jenkinsEnv.sh > export JAVA_HOME="$saveJavaHome" > export PATH=$JAVA_HOME/bin:$PATH > which java > java -version > echo "Resetting java_home -- FIX jenkinsEnv.sh!!! $JAVA_HOME" > .... > {code} > HBase builds on hadoop1||hadoop2||hadoop3||hadoop8 > I ain't sure how this stuff is supposed to be set. Asking Andrew Bayer on our end (He said 'credits' needed refresh last night but that doesn't seem to have helped here). -- This message was sent by Atlassian JIRA (v6.2#6252)