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

Reid Chan commented on HBASE-20068:
-----------------------------------

LGTM.

> Hadoopcheck project health check uses default maven repo instead of yetus 
> managed ones
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-20068
>                 URL: https://issues.apache.org/jira/browse/HBASE-20068
>             Project: HBase
>          Issue Type: Bug
>          Components: community, test
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Major
>         Attachments: HBASE-20068.0.patch, HBASE-20068.1.patch
>
>
> Recently had a precommit run fail hadoop check for all 3 versions with 
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-install-plugin:2.5.2:install (default-install) 
> on project hbase-thrift: Failed to install metadata 
> org.apache.hbase:hbase-thrift:3.0.0-SNAPSHOT/maven-metadata.xml: Could not 
> parse metadata 
> /home/jenkins/.m2/repository/org/apache/hbase/hbase-thrift/3.0.0-SNAPSHOT/maven-metadata-local.xml:
>  in epilog non whitespace content is not allowed but got / (position: END_TAG 
> seen ...</metadata>\n/... @25:2)  -> [Help 1]
> {code}
> Looks like maven repo corruption.
> Also the path {{/home/jenkins/.m2/repository}} means that those invocations 
> are using the jenkins user repo, which isn't safe since there are multiple 
> executors. either the plugin isn't using the yetus provided maven repo path 
> or our yetus invocation isn't telling yetus to provide its own maven repo 
> path.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to