-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
OSX 10.8.2
When I execute a build using a Maven 3 project, the initial checkout/out works fine (referencing "hg" using its full path) but subsequently the build fails as follows:
[INFO] --- maven-release-plugin:2.1:perform (default-cli) @ cmake --- [INFO] Checking out the project to perform the release ... [INFO] Removing /Users/builds/.jenkins/workspace/cmake/target/checkout [INFO] EXECUTING: /bin/sh -c cd /Users/builds/.jenkins/workspace/cmake/target && hg clone -r release-2.8.10-b1 https://cmake-maven-project.googlecode.com/hg/ /Users/builds/.jenkins/workspace/cmake/target/checkout [ERROR] EXECUTION FAILED Execution of cmd : clone failed with exit code: 127. Working directory was: /Users/builds/.jenkins/workspace/cmake/target Your Hg installation seems to be valid and complete. Hg version: NA (OK)
In other words, it looks like Jenkins is smart enough to reference hg using its full path, but the hg scm vendor (used by "release:perform" goal) assumes "hg" is on the PATH.
I couldn't find a workaround. I found one other discussion thread but no solution: http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-td5463712.html
To reproduce the problem, create a Maven3 project with the following build task:
"clean:clean release:clean release:perform -Pmac -Dtag=release-2.8.10-b1 -DconnectionUrl=scm:hg:https://cmake-maven-project.googlecode.com/hg/"