TeamCity SVN always clean-up?

"Clean all files before build" is NOT checked.

Everytime a build start, I see the complete directory disappear and download (update) all the source code from the SVN repository. I have tested with 1 file modification of 1 line and it still clean all files! This is wasting a lot of time.

What should I do?

9 comments
Comment actions Permalink

Do you use custom checkout directory? If so is there any other build configuration which uses the same checkout directory?

--
Pavel Sher

0
Comment actions Permalink

I do not believe I use Custom Check out (I have check the Version Control Setting and the VSC Checkout Rule and both doesn't have an option like that, so I guess I am not.

The build has a unique directory in the c:\svn\nightbuild\

0
Comment actions Permalink

Could you please submit your build configuration settings (settings tab on the build configuration page) and build log?

--
Pavel Sher

0
Comment actions Permalink

I have changed the Clean-Up process settings (Adminitration>Build History Clean-Up) to disable and since that time the night build doesn't take all the SVN directory. I do not know if it's a coincidence or not. For the moment, the files aren't deleted any more. I found it stranges but well thx for all input I think the problem is solve.

0
Comment actions Permalink

Cleanup process just removes VCS caches from the disk, and if your build always takes all sources from the repository this can affect its performance. However as I understood you you do not want your build to take all the sources, it should take changes only, am I right? That is why I asked you to provide your build configuration settings, without them I cannot tell why you experience such behavior.

--
Pavel Sher

0
Comment actions Permalink

Yes you are right.

Version Control Setting

http://clip2net.com/clip/m12122/1228747081-clip-25kb.png

SVN configuration:

http://clip2net.com/clip/m12122/1228747291-clip-32kb.png

Is that what you desire to see?

0
Comment actions Permalink

As I can see you are using custom checkout directory, are you absolutely sure that no one other build configuration has the same checkout directory but different VCS root or checkout rules?

--
Pavel Sher

0
Comment actions Permalink

Might be my fault! I just noticed a test buil when people commit the system. This might be the one who cleaned up all the files... but hummm  I checked and the configuration has not the "Clean all files befoire build" too. If those two build are in conflict I think I need to simply use 2 differents directory (Checkout directory) and the problem will be definetly over right?

0
Comment actions Permalink

Actually to avoid such problems and to better reuse disk on agents you may not specify checkout directory at all. In this case TeamCity will generate directory names automatically and there will not be any conflicts if build configurations use different VCS roots. At the same time if two configurations use the same root then the directory will be reused among them and less disk space will be occupied. So if your build or tests are not tied up to some specific directory I would suggest you to leave this field blank.

--
Pavel Sher

0

Please sign in to leave a comment.