-
Bug
-
Resolution: Not A Defect
-
Blocker
-
None
-
Jenkins 1.512 / JDK 1.7 / Debian 6 / x86
Issued a try run. Jenkins checks SVN and says there are no differences, then runs Maven. After Maven is finished, there is a stack trace:
...
Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to check for local modifications
Provider message:
The svn command failed.
Command output:
/bin/sh: svn: not found
at org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.execute(ScmCheckModificationsPhase.java:109)
at org.apache.maven.shared.release.phase.ScmCheckModificationsPhase.simulate(ScmCheckModificationsPhase.java:154)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:199)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140)
at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103)
at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211)
... 30 more
The funny thing is that Jenkins can use svn, but Maven cannot? Strange!
[JENKINS-17856] Cannot find svn
Would be great if you could add a clear note on the plugin's web page that to use it with SVN, it is essential to manually install SVN on the master and all server nodes, or the above message will appear. I think I am not the only one that did not know that the Jenkins-distributed MVN does not use the same SVN implementation that Jenkins uses! 
Jenkins does not use the svn command, but rather it has inbuilt Java code.
The release is performed by maven, so access is required to tools required by maven.