![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
teilo
|
|
Components:
|
m2release |
|
Created:
|
03/May/13 5:58 PM
|
|
Description:
|
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!
|
|
Environment:
|
Jenkins 1.512 / JDK 1.7 / Debian 6 / x86
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Blocker]() Blocker
|
|
Reporter:
|
Markus KARG
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
