[JIRA] (JENKINS-10222) Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)

[andr...@semanticedge.de (JIRA)]

Andreas Schoen commented on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) I had the same problem with a project with the Repository URL of the following pattern: svn://<servername>/applications/xxx//trunk/yyy The polling message was: Workspace doesn't contain svn://<servername>/applications/xxx//trunk/yyy. Need a new build. However, the polling did work successfully (no changes, at revision...) when I set the Repository URL to svn://<servername>/applications/xxx/trunk/yyy (without the second slash after xxx). It seems that the repository url in the working copy is normalized (e.g. removing double slashes, port number) by the svn client, but the check if the working copy matches the project does not perform this kind of normalization. Jenkins ver. 1.471 Subversion Plugin version 1.4

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