Project requires frequent "clean checkout" with SVN

Does anyone else experience the need to frequently "enforce clean checkout" when using SVN? It seems that our teamcity build fails fairly frequently due to resources not being present in the build agent's working copy. None of our development team experiences the problems when they update their own working copies and this is a cause of some concern. We are using the default VCS settings and we don't have any checkout rules. Any suggestions would be much appreciated.

Thanks,

David

3 comments
Comment actions Permalink

I have seen this recently too...I have one project that has 2 SVN VCS Roots. Each has a simple checkout rule to force the checkout to a certain folder. Every second build, 1 of the VCS roots is not checked out...

I have not yet had a chance to file a bug report...

Scott

0
Comment actions Permalink

Our situation is less regular than that but it's still quite frequent - I'd guess one of every 10 or so builds fails because some files are not updated from SVN and the only solution is to build again with clean sources. There doesn't seem to be any pattern to the failures as far as I can tell. If you do file a bug, please let me know the tracking # so I can watch it. Thanks :)

0
Comment actions Permalink

I would recommend you to submit bug to our tracker. Please describe your vcs roots settings (you can provide screenshot of VCS root and screenshot of VCS settings page in build configuration). Also please enable logging: http://www.jetbrains.net/confluence/display/TCD4/Reporting+Issues#ReportingIssues-VersionControlDebugLogging and try to reproduce bug. After that please attach teamcity-vcs.log and teamcity-server.log to the issue.

--
Pavel Sher

0

Please sign in to leave a comment.