Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-20068

Hadoopcheck project health check uses default maven repo instead of yetus managed ones

    XMLWordPrintableJSON

    Details

      Description

      Recently had a precommit run fail hadoop check for all 3 versions with

      
      [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]
      

      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.

        Attachments

        1. HBASE-20068.0.patch
          2 kB
          Sean Busbey
        2. HBASE-20068.1.patch
          3 kB
          Sean Busbey

          Activity

            People

            • Assignee:
              busbey Sean Busbey
              Reporter:
              busbey Sean Busbey
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: