"Error collecting changes" in VCS when external folders are moved or deleted

Teamcity 5.0, using subversion.

We're regularly seeing an issue if a developer moves the location of, or removes an external from, an existing VCS that Teamcity gets stuck trying to check out the latest version of the original folder, which of course no longer exists. Clearing the cache makes no difference, nor does changing any of checkout settings (clean, checkout on agent/server, etc.)

Eventually (days) the error clears, but that's no comfort to the developer who has an urgent bugfix to release...

Any suggestions on what to do to tell Teamcity to forget about the old external location?

Comment actions Permalink

Hello Ben,

   What you're describing is a bug which we have to fix. I'd appreciate if you provide details on how to reproduce the issue to our tracker.



Please sign in to leave a comment.