-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Git plugin 1.5.0 on Jenkins 1.509.4
We have several Maven jobs, and on a new one we set up in the past few days we are seeing some strange errors in the Git polling log. Much of the time the Git polling works fine, but several times per day we get this error (see attached from Git polling log).
The "mavenHome" path mentioned in the error message is a valid path on the master, but not on the slaves where this job is actually running (the slave has a significantly different directory structure than the master). I have set the "tool location" for Maven on the slaves to the correct location.
The message in the stack trace is "Unable to determine maven version". The exception is generated through a call to GitSCM, but the root problem seems to be in the maven version reading code used on the slave node, not in the Git plugin.