TeamCity 7.0.4

Maria Khalusova

One more bug-fix update is available – TeamCity 7.0.4. This build comes with a number of general fixes, addresses a few performance issues, and additionally introduces one small feature – an ability to fail a build based on statements from dotCover coverage with “Fail build on metric” build failure condition (TW-21111).

To see the complete list of fixed issues, please refer to the release notes.
Download the build and share your feedback with us.

Comments below can no longer be edited.

5 Responses to TeamCity 7.0.4

  1. Halstein Tonheim says:

    July 13, 2012

    One comment to TW-21111:
    In the bug report I added a workaround to the issue. The workaround was to add to the element in the /config/main-config.xml file. If this workaround was used, TeamCity will no longer start after upgrading to 7.0.4. Instead TeamCity will display an error message saying CodeCoverageS cannot be added because it already exists.

    To fix this, open /config/main-config.xml and remove . If this was your only entry between the build-metrics element, you can just remove the entire block. Once this is removed from the main-config.xml file you have to restart TeamCity. In Windows this is done by restarting the TeamCity service in Control Panel->Administration tools->Services. Then just access the TeamCity web page again and all should be fine.

  2. Halstein Tonheim says:

    July 13, 2012

    Seems like all the xml in my previous comment go removed. Therefore I just added the fix for the issue as a comment to TW-21111. Just go there to find a less confusing solution description if your TeamCity installation now crashes because CodeCoverageS already exists.

  3. Simon Hurley says:

    July 13, 2012

    Just upgraded from 6.5.6 to this an hour or so ago with 127 projects, with 541 build configurations. the projects page appears nice and quick, the rest of the site, is much slower.

  4. pavel.sher says:

    July 13, 2012

    Simon, please provide more details by email ( or in our forum ( This should be useful as well:

  5. pavel.sher says:

    July 13, 2012

    Halstein, thank you for update. I created issue for this case:


Subscribe for updates