CI on same machine as build/repository?

Hello,

The disadvantages I can think of are:

- slower access to TeamCity UI when your build is running
- worse estimation for your build duration time because it is affected by server load caused by access to TeamCity UI

In-house, we have a build agent which runs on the same machine as TeamCity server. But this agent has the only one task - to upgrade TeamCity installation we run locally. If interested, you can read more at http://teamcitydev.blogspot.com/2008/08/you-probably-have-seen-this.html

Kind regards,
KIR

Thanks for the reply. That makes sense.

I haven't used TC yet and have yet to actually configure a CI myself so bare with me. My other question is how do you access the build output remotely? (assuming you're build, msbuild/nant or whatever is on the same box as the projects)

In fact, it doesn't matter whether build is run on the same machine or on another computer.
TeamCity build agents pass build output and other details to the main server while build is running,
so you have immediate access to build log, test details while build is running. The data is sent via XML-RPC protocol.

You may take a look on the TeamCity UI at http://teamcity.jetbrains.com
Or, better, try it yourself :)

Regards,
KIR

Thanks.

We plan to try TC but didn't want to install it on the same machine until we had found out whether it should be on it's own machine first. Another machine won't be available for a couple days so I wanted to check on the best practice for setup. It sounded like from your first post that it's best to put TC on a separate machine as the msbuild/Nant processes.

Does TC build the projects also or will I still need msbuild?

TeamCity uses external tools to build projects.
List of build runners is available at
http://www.jetbrains.net/confluence/display/TCD3/TeamCity+Documentation

For MSBuild settings, see http://www.jetbrains.net/confluence/display/TCD3/MSBuild

Regards,
KIR

When is the TC 4 release expected?

Hopefully, in this year. So you're encouraged to try our EAP builds :)

That's why I asked. Although I'm not big on putting non-release candidates in production.