[ https://issues.apache.org/jira/browse/HBASE-20068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434351#comment-16434351 ]
Hudson commented on HBASE-20068: -------------------------------- Results for branch branch-1.4 [build #284 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/284/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (x) {color:red}-1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/284//General_Nightly_Build_Report/] (x) {color:red}-1 jdk7 checks{color} -- For more information [see jdk7 report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/284//JDK7_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/284//JDK8_Nightly_Build_Report_(Hadoop2)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. > 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 > Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.4, 2.0.1 > > 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)