You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/09/15 16:15:46 UTC
[jira] [Comment Edited] (INFRA-10429) Hadoop machines have lost mvn
[ https://issues.apache.org/jira/browse/INFRA-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745521#comment-14745521 ]
Sean Busbey edited comment on INFRA-10429 at 9/15/15 2:15 PM:
--------------------------------------------------------------
We've been setting MAVEN_HOME in [this script file|https://github.com/apache/hbase/blob/master/dev-support/jenkinsEnv.sh#L30] to point at /home/jenkins/tools/maven/latest.
In the precommit job I started exporting MAVEN_3_0_5_HOME and I updated the shell step to set MAVEN_HOME to point at that variable's content. I think that's our current minimum supported Maven version?
I *think* it's still not getting put on the path, but my connection in this airplane is currently too spotty to fix that part. I'll keep trying.
was (Author: busbey):
We've been setting MAVEN_HOME in [this script file |https://github.com/apache/hbase/blob/master/dev-support/jenkinsEnv.sh#L30] to point at /home/jenkins/tools/maven/latest.
In the precommit job I started exporting MAVEN_3_0_5_HOME and I updated the shell step to set MAVEN_HOME to point at that variable's content. I think that's our current minimum supported Maven version?
I *think* it's still not getting put on the path, but my connection in this airplane is currently too spotty to fix that part. I'll keep trying.
> Hadoop machines have lost mvn
> -----------------------------
>
> Key: INFRA-10429
> URL: https://issues.apache.org/jira/browse/INFRA-10429
> Project: Infrastructure
> Issue Type: Bug
> Components: Buildbot
> Reporter: stack
>
> These machines no longer have mvn in their path when we build:
> H0 && H10 && H2 && H6 && H5 && H4
> When our patch build runs it says:
> /home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/test-framework/dev-support/test-patch.sh: line 861: mvn: command not found
> .... on these machines. Other H? machines seem to have mvn fine.
> Here is what our patch script does trying to find mvn:
> 27 # Defaults
> 28 if [ -z "$MAVEN_HOME" ]; then
> 29 MVN=mvn
> 30 else
> 31 MVN=$MAVEN_HOME/bin/mvn
> 32 fi
> If I try to print out 'which mvn' before our build starts, it seems to come up blank.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)