teamcity

I've been working on the next step of my continuous integration project, which is to get TeamCity to build my application, automatically change the version number of all assemblies, and then create an installer. A little background first: I've been running TeamCity successfully for the past several months, and it builds my configurations and runs my NUnit and NCover tests just fine. I took a little time researching installers -- I have always hated InstallShield and never considered it for my current application. I like NSIS, but then happened to come across WiX . I don't have any intimate

I use TeamCity to build c++ on Unix (Solaris). TeamCity invokes make, and within my makefile I need to call svn . For this I need to modify PATH and LD_LIBRARY_PATH . I could set these within the makefile but the locations vary from server to server. does anyone know a way to set these for each TeamCity build agent, e.g. by editing conf/buildAgent.properties ? I could set them in ~/.login etc for the TeamCity build account, but I would prefer not to as it is a shared account. -thanks, Barney You could create a wrapper script that exports these variables before executing the TeamCity command.

From looking at the TeamCity REST API Documentation , the request for statistical data is: http://teamcity:8111/httpAuth/app/rest/builds/<buildLocator>/statistics/ Which works, however , it only gives statistics for the current build (tests passed, code coverage, number of duplicates, etc.), I am looking to build a graph for my build radiator showing trends, therefore I want the historical data for the past month. Is there a way to get this historical statistic data from the TeamCity API? Rather than hit the DB directly, you can get at the data via the exportchart endpoint on TeamCity. This is

What is the best way to run and report Visual Studio 2012 code analysis in TeamCity? Since FxCop or Code Analysis integrates directly into MsBuild, it's probably as simple as adding /p:RunCodeAnalysis=Always or /p:RunCodeAnalysis=True to the MsBuild commandline when building the project. Since this will generate standard compiler warnings, TeamCity should pick them up automatically. Visual Studio 2010+ Code Analysis is (based on) FxCop 10.0. You can simply add a 'FxCop' build runner type build step. When the 'Report XSLT file' setting is configured the build runner will output a HTML report.