I know this has come up in the past but I am on the latest version of TeamCity (9.0.2). As an example, for one of our SVN updates (using fast update+always revert setting) takes around 5-10mins. If I use the command line revert it takes around 10 seconds. See pictures below:
USING BUILT IN REVERT
USING COMMAND LINE REVERT
The difference is simply unacceptable as this is run for every check-in and for our teamsize we have a check in every 20-30mins for ALL the projects we have and the difference adds on very substatntially (we have a build chain of around 30 items.
One of the the problem with running a manual revert as a build step (and it is not desirable anyways) is that Swabra is run before the build step and will result in wrong data. We have tried to optimize it by using limited checkouts as shown below but as you can see the update still takes out 2.5 minutes for a smaller project.
We tried using working copy format 1.8 and 1.7 but has no effect.
Is this a performance issue in TeamCity? If yes, when is it planned to be resolved.Our build chains are large and currently SVN checout/revert is the biggest bottleneck....