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

[damien.finc...@online.fr (JIRA)]

Damien Finck edited a comment on JENKINS-10222 Jenkins cleaning out workspace unnecessarily when polling SCM (SVN) Hello, I have exactly the same problem. In Jenkins, I have about 30 projects. For two of my projects, I have this problem for some time. The first one has this configuration: An SVN repository on "https://<company>.fr:433/svn/<project>" in the folder "trunk" of my workspace "Use 'svn update' as much as possible" And at each build, Jenkins said "Checking out a fresh workspace Because The workspace is not "https://<company>.fr:443/svn/<project>" " For the second project that is the problem, it is configured this way: 3 SVN repositories https://<company>.fr/svn/<project1> in the folder "project1" https://<company>.fr:433/svn/<project2> in the "Project2" https://<company>.fr:433/svn/<project3> in the "project3" "Use 'svn update' as much as possible" And at each build, Jenkins said "Checking out a fresh workspace Because The workspace is not "https://<company>.fr:443/svn/<project3>" " I have a problem only on the third repositorie. I tried to remove the first project and recreate it: Same problem. I read in a forum user who said: "I had a similar problem .... but It Was Because The name of the SVN server in my path Was in CAPS. I changed it to lower case and it worked. ... " So, I changed my path from https://<company>.fr:433/svn/<folder> to https://<company>.fr/svn/<folder> and it works in my two projects . It like if repositorie has once time a bug, Jenkins do each other time a "svn checkout" on this repositorie instead of an "svn update". Version : Jenkins : 1.474 Jenkins Subversion Plug-in : 1.42 Subversion version (in Jenkins configuration) : 1.7 Sincerely, Damien

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