0

We have a TFS2010 instance that is hosted overseas. We have a proxy locally so pulling source code is really no problem. Even full gets are quite speedy. One issue that we are experiencing is that when an automated build completes it takes forever for the test results to be published back to the server. The entire build and test process takes about 5 minutes. The publishing of the test results takes an additional 10 minutes. Twice the time it took to get the source, build it, and run all 1500 unit tests!

Is there any way I can speed this up?

dbc
  • 104,963
  • 20
  • 228
  • 340
Adam Driscoll
  • 9,395
  • 9
  • 61
  • 104
  • Is there a reason the build server isn't located on the site as the TFS server? Once the build is complete you can copy the compiled output and deploy to local test servers as and when needed. – Richard Banks Nov 25 '10 at 21:58
  • The main reason is convenience. The TFS server is located in a data center with strict regulations. The build server is local for accessibility. – Adam Driscoll Nov 29 '10 at 16:27

1 Answers1

0

Try setting up a build agent at your location and set a name filter in the build definition to always select that build agent.

LeWoody
  • 3,593
  • 4
  • 25
  • 31
  • I guess my question wasn't clear. The TFS server is remote while the build agent is local. Sorry for the confusion! – Adam Driscoll Nov 29 '10 at 16:13
  • Then it's probably because the build definition has to store the results in the TFS database before reporting it to you; which means a round trip to the remote, central TFS server. – LeWoody Dec 03 '10 at 21:26