www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-12405) Maven versions are not available on all build machines
Date Wed, 10 Aug 2016 16:41:20 GMT

     [ https://issues.apache.org/jira/browse/INFRA-12405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maximilian Michels updated INFRA-12405:
---------------------------------------
    Status: Waiting for Infra  (was: Waiting for user)

I'm getting the following exception, even though I'm using the "Maven 3.2.5" label:

java.lang.IllegalArgumentException: /home/jenkins/tools/maven/apache-maven-3.2.5 doesn't have
a 'lib' subdirectory - thus cannot be a valid maven installation!
    at hudson.maven.MavenEmbedderUtils.buildClassRealm(MavenEmbedderUtils.java:83)
    at hudson.maven.MavenEmbedderUtils.getMavenVersion(MavenEmbedderUtils.java:188)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:70)
    at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:42)
    at hudson.remoting.UserRequest.perform(UserRequest.java:120)
    at hudson.remoting.UserRequest.perform(UserRequest.java:48)
    at hudson.remoting.Request$2.run(Request.java:326)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
    at ......remote call to H11(Native Method)
    at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
    at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
    at hudson.remoting.Channel.call(Channel.java:781)
    at hudson.FilePath.act(FilePath.java:1074)
    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:629)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
    at hudson.model.Run.execute(Run.java:1738)
    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)

> Maven versions are not available on all build machines
> ------------------------------------------------------
>
>                 Key: INFRA-12405
>                 URL: https://issues.apache.org/jira/browse/INFRA-12405
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Maximilian Michels
>            Assignee: Gavin
>
> On Jenkins, we want to build with a specific Maven version. So we set the appropriate
Maven version through an environment variable.
> Then we change the PATH to load the specific maven version, like this:
> export PATH="$MAVEN_3_2_5_HOME/bin:$PATH"
> This stopped working and our Maven script can't find the Maven binaries anymore. Which
Maven versions are expected to be available on the build slaves?
> https://builds.apache.org/job/flink-snapshot-deployment/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message