JetBrains launch TeamCity blog
Author: Glenn Slaven11 Apr
JetBrains have created a dedicated blog for TeamCity, their continuous integration and build management tool. I downloaded the 2.0 beta for TeamCity last week and set up an integration build for the Drive web solution. It’s brilliant, so simple. It automatically watches the subversion repository and rebuilds on each checkin, showing all the changes in the files with a side-by-side diff screen. It can auto-run unit tests and report build status to either email, a system tray app or even a Jabber account!
From the looks of the application, once it gets released to production it could handle our whole build cycle from development all the way to deployment, because it can not only build Visual Studio solution files, but also run NAnt scripts or even just a command line app. The build processing is ingenious too. Rather than having to do all work on the server, you can install a client app on multiple computers that connect to the server which can be used to do builds, so that multiple builds can be happening at once. The diffent builds can be done on specific clients depending on platform and other environment variable targets that can be setup in the build, so you could have a Windows 2003 build and a Linux build running off the one server but they will be built by the appropriate client machine at the time specified (either on check-in or scheduled).
TeamCity costs US$199, which will include the 2.0 release.
- Filed under: General, Tags: build management, JetBrains, NET, TeamCity
- Video games Australia Buy video games from stores in Australia
- Software Australia Comapre and buy software in Australia
8 Responses for "JetBrains launch TeamCity blog"
We use the combination of SVN, CruiseControl.NET, NAnt & NUnit to do the same sort of thing and it works a treat.
I do like the idea of being able to farm out the build process though, that is very nice.
Yeah, we were looking at that too, but unfortunatelyNAnt doesn’t do 2.0 solution file builds 
We use the combination of SVN, CruiseControl.NET, NAnt & NUnit to do the same sort of thing and it works a treat.
I do like the idea of being able to farm out the build process though, that is very nice.
Yeah, we were looking at that too, but unfortunately <ah ref=”http://nant.sourceforge.net/release/latest/help/tasks/solution.html”>NAnt doesn’t do 2.0 solution file builds
</ah>
What kind of trouble were you having with NAnt and 2.0? I’ve had nant-0.85rc3 doing 2.0-framework builds since early ‘06 for a client of mine. I recall having to fiddle with the bin\nant.exe.config to cobble up a 2.0 framework section, but it was pretty much a copy/paste job, and replacing the 1.1.4322 strings with 2.0.50727 strings. Hope this helps.
Cheers,
-chris
What kind of trouble were you having with NAnt and 2.0? I’ve had nant-0.85rc3 doing 2.0-framework builds since early ‘06 for a client of mine. I recall having to fiddle with the binnant.exe.config to cobble up a 2.0 framework section, but it was pretty much a copy/paste job, and replacing the 1.1.4322 strings with 2.0.50727 strings. Hope this helps.
Cheers,
-chris
I want to be able to use the solution command to compile a whole solution, you could do it with 1.1, but not in 2.0. Thanks, but we worked out a solution where we use the nant script to build each project.
I want to be able to use the solution command to compile a whole solution, you could do it with 1.1, but not in 2.0. Thanks, but we worked out a solution where we use the nant script to build each project.
Leave a reply