www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10429) Hadoop machines have lost mvn
Date Tue, 15 Sep 2015 13:01:45 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745418#comment-14745418
] 

stack commented on INFRA-10429:
-------------------------------

I thought it was ok that we had concurrent builds running on same box. IIRC, we were warned
that was going to happen going forward so have dealt (we used to think we were going to be
only build on a box... )

> 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)

Mime
View raw message