[
https://issues.jenkins-ci.org/browse/JENKINS-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163655#comment-163655
]
Damien Finck commented on JENKINS-10222:
----------------------------------------
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".
Sincerely,
Damien
> Jenkins cleaning out workspace unnecessarily when polling SCM (SVN)
> -------------------------------------------------------------------
>
> Key: JENKINS-10222
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10222
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Environment: Windows
> Reporter: Giles Dermody
>
> I am using a SVN repository which is being checked out at the beginning of
> every build in a Jenkins job. It is set to "poll SCM" for updates. However,
> regardless of whether there were changes or not it is cleaning out the
> workspace and downloading the whole repository in it's entirety every time
> which is unnecessary.
> Builds are taking much longer than they should as the SVN poll should only be
> checking out newly-updated files. Sample log:
> Checking out a fresh workspace because the workspace is not
> file://PICKLE/Repositories/project
> Cleaning workspace.....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
