-
Bug
-
Resolution: Unresolved
-
Critical
When RedeployPublisher deploys packages to Maven repository, it trying to create the ~/.m2 directory on the Master. This behavior doesn't depends on the "Use private Maven repository" option.
Build log:
Maven RedeployPublished use remote <slave> maven settings from : <Remote FS root>/tools/Maven_3.0.3/conf/settings.xml ERROR: Publisher hudson.maven.RedeployPublisher aborted due to exception hudson.AbortException: Failed to create <Master user.home>/.m2 See https://hudson.dev.java.net/cannot-create-.m2.html at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:151) at hudson.maven.RedeployPublisher.createEmbedder(RedeployPublisher.java:296) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:668) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:953) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:615) at hudson.model.Run.run(Run.java:1401) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:474) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)
This behavior isn't suitable, if we don't have Maven on the Master, accordingly the ~/.m2 directory doesn't exist. Why this directory needed on the Master?
- is related to
-
JENKINS-4940 Maven2 build checks for ~/.m2 existence
- Open