Please ignore this issue! It turned out to be an issue in my own code. I was able to find it and fix it after so heavy debugging.
-James On Wednesday, February 26, 2014 1:14:38 PM UTC-5, Dominik Bartholdi wrote: > > Any reason for using such an old Jenkins version? Why don’t you use a LTS? > Domi > > On 26.02.2014, at 17:48, James Richard <jamesri...@gmail.com <javascript:>> > wrote: > > Hello, > I am developing a plugin for Jenkins. I am using Jenkins 1.396, and I > am running a Free Style Build. When I run my plugin on a slave and I > Invoke top-level Maven targets as my build step with "clean install" as the > goals, I get this error: (I replaced most of the directory path with ... > for privacy, the full path that was defined in the global configuration was > what actually appeared in the error message) > > [ERROR] hudson.AbortException: Maven Home ..../maven-3.0.4 doesn’t exist > hudson.AbortException: Maven Home ..../maven-3.0.4 doesn’t exist > at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:68) > at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:42) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:328) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at hudson.remoting.Engine$1$1.run(Engine.java:63) > at java.lang.Thread.run(Thread.java:662) > > > and it says my Maven Home does not exist. When I configure the slave I > added the tool location for this specific Maven 3 builder but in the error > it prints out the home directory for Maven that was defined in the global > configuration. It is ignoring the tool location that was defined in the > slave configuration. I have also set up this job to pull from git and the > tool location for that works fine for the slave. > > Can anyone point me to a Jira ticket for this issue? I found this one > for Maven 2 : https://issues.jenkins-ci.org/browse/JENKINS-3199 but it > seems to be broken for Maven 3. Was this fixed in a later version of > Jenkins? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-de...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.