---
title: "Trying out Team City - Looks Promising!"
url: "https://osherove.com/blog/2008/1/18/trying-out-team-city-looks-promising.md"
canonical: "https://osherove.com/blog/2008/1/18/trying-out-team-city-looks-promising.html"
published: "2008-01-18T17:36:17"
updated: "2008-01-18T17:36:17"
tags: ["Agile", "General Software Devel..."]
author: "Roy Osherove"
description: "I've been looking both at CI Factory by Jay Flowers , and Team City by JetBrains lately. this has to do with the fact that at Typemock we currently have a Continuous Integration solution that is largely based on…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Trying out Team City - Looks Promising!

By Roy Osherove January 18, 2008 In [Agile](https://osherove.com/blog/category/agile), [General Software Devel...](https://osherove.com/blog/category/general-software-devel)

**Historical article** · Originally published January 18, 2008; technical details may be outdated.

I've been looking both at [CI Factory](http://www.cifactory.org/joomla/) by [Jay Flowers](http://jayflowers.com/), and [Team City by JetBrains](http://www.jetbrains.com/teamcity/) lately. this has to do with the fact that at Typemock we currently have a [Continuous Integration](http://en.wikipedia.org/wiki/Continuous_integration) solution that is largely based on [CruiseControl.NET](http://cruisecontrol.sourceforge.net/) and MSBuild files.

It sucks.

The MSBuild files are hardly maintainable and the logic for running the build, signing things, obfuscating, licensing, installation, 64 bit versions and more - it's chaos, held by some gum and a couple of strings. Not unlike many other builds I've seen.

We're in the process of moving the builds into [FinalBuilder](http://finalbuilder.com/), but I'm also looking for a better CC.NET. CI Factory looks nice in that it is very simple to setup but still requires messing around with MSBuild targets and the like to make your builds work with it.

TeamCity looks very promising. I read [this blog post from Elutian](http://blog.eleutian.com/2007/12/22/CruiseControlNETIsDeadLongLiveTeamCity.aspx) about their experience with Team City and wondered what it would be like to work with it against a FinalBuilder script. I installed TeamCity and ran it against SVN and FinalBuilder (like it would run at Typemock) and got it all working in less than 20 minutes. Pretty snazzy and no XML tampering needed to take place, Thank the gods.

The killer feature in Team City?

[Delayed Commit](http://www.jetbrains.com/teamcity/features/newfeatures.html#Improved_Quality_Maintenance)(also known as private build). It allows you to run the full build with tests on the server as if you checked in all your changes, but **without actually checking in your changes until the build is successful,** so you will know if you're about to break the build before you actually break it.

So, I'm thinking, with team city's professional license being **free** for up to 20 developers and 3 build agents, that we'll give it a shot at Typemock HQ and see what happens.

## More in Agile

[All posts in Agile](https://osherove.com/blog/category/agile)

- Jan 20, 2008

    ### [The Case For Typemock](https://osherove.com/blog/2008/1/20/the-case-for-typemock.html)

- Jan 20, 2008

    ### [TDD Anti Patterns](https://osherove.com/blog/2008/1/20/tdd-anti-patterns.html)

- Jan 17, 2008

    ### [Is Typemock too powerful? Will it kill design for testability?](https://osherove.com/blog/2008/1/17/is-typemock-too-powerful-will-it-kill-design-for-testability.html)

- Jan 17, 2008

    ### [The evolution of Unit Testing Syntax and Semantics](https://osherove.com/blog/2008/1/17/the-evolution-of-unit-testing-syntax-and-semantics.html)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/
