teamcity

问题 I have two separate projects from two separate TFS VCS roots that I want to be part of the same build and was wondering if this is possible. Project 1 VCS Root: $/ProductName/Development/Project1 Build file path: API/API.sln Project 2: VCS Root: $/QA/Test/Tools/Project2 Build file path: Test/Test.sln I want step #1 of the build to compile Project 1, and step #2 to compile Project 2. How can I do this if the build file path is relative to the VCS root/checkout directory and the solutions are

问题 I have created unitests using import unittest. When I want to run a specific test and I put a breakpoint then go to the console and try to eval expressions there's no return value as if the stdout is no longer the console screen. I have never installed teamcity but strangely I do get messages when running the unittest. VERY STRANGE. I thought that maybe the captureStandardOutput='true' (emphasized on last line, below) is the cause of the problem but I can't even find where to change the param

问题 What's the best way to move a single TeamCity build configuration from one server to another? I have a local instance of TeamCity that I test builds on. Then when the build is sufficiently mature, I manually create it (eyeball-copy) on our main TeamCity server. Is there an Export & Import feature that will do this for me? 回答1: Unfortunately there is no such thing. TeamCity 8 made the situation a little bit better though by introducing a Build Id format (project name + build config name, can

问题 I'm trying to run a custom command in my MSBuild file; it basically runs 'git log -10' and stores that commit info into a text file. The problem is, when I try to run the build, it errors saying "fatal: Not a git repository". So I checked TeamCity's work directory for my project, and there is no .git directory! Why doesn't TeamCity create the .git directory when it clones the repository? Is there a way to enable this? edit: TeamCity version is 7.1.2; I'll try updating to 8.0.1 to see if there

问题 How do I run MSTest as part of my build process in TeamCity? What are the pitfalls? 回答1: This answer is specifically for TeamCity 7.1 on Windows, but may apply to other environments. In your TeamCity build configuration, on the General Settings page Artifact paths : Artifacts\MSTest => MSTest Create a new Command Linebuild step Custom script : if not exist Artifacts\MSTest mkdir Artifacts\MSTest Create a new MSTestbuild step List assembly files : **\bin\**\*.Tests.dll Results file : Artifacts

问题 We are developing an application framework + "plugins" using TeamCity as a CI server. Project Details 4 Visual Studio solutions ~70 projects (and increasing) Currently running 2 builds using TeamCity: CI and FULL build. CI - triggered on every commit. FULL - runs nightly. I would like to improve the performance of both builds (especially the CI build, as it needs to give its output as quickly as possible). Are there any guidelines in general on what can be effectively and easily improved? The

问题 I'm having a few problems breaking out an MsBuild package+deploy command into two separate commands. (I need to do this to pass additional parameters to MsDeploy). The command that works fine looks like this: msbuild "src\Solution.sln" /P:Configuration=Deploy-Staging /P:DeployOnBuild=True /P:DeployTarget=MSDeployPublish /P:MsDeployServiceUrl=https://192.168.0.1:8172/MsDeploy.axd /P:DeployIISAppPath=staging.website.com /P:AllowUntrustedCertificate=True /P:MSDeployPublishMethod=WmSvc /P

问题 Continuous integration concept has just been integrated in my team. Assume we have an integration branch named Dev . From it derived 3 branches, one for each specific current project : Project A Project B Project C First, Teamcity is configured on a dedicated server and it goals is : Compiles and launches unit and integration tests from versioned sources from each branch including Dev Then, of course, each project branch (A,B and C) must be tested in a cloned production environment so that

问题 I want to provide a git tag to the TeamCity server to build it. I pass the tag (i.e. release_1.1 ) as a parameter to the job. So inside the job the tag is available as %tag% , but under the Version Control Settings I don't see any way to use this parameter so the server can checkout this tag. Is there any way this parameter can be used in the settings to checkout the tag? 回答1: Go to Edit Configuration Settings -> Version Control Settings For all your VCS roots for this build configuration

问题 I have some XML that looks something like this: <?xml version="1.0" encoding="utf-8"?> <XmlConfig instancetype="XmlConfig, Processing, Version=1.0.0.0, Culture=neutral"> <item> <key>IsTestEnvironment</key> <value>True</value> <encrypted>False</encrypted> </item> <item> <key>HlrFtpPutDir</key> <value>C:\DevPath1</value> <encrypted>False</encrypted> </item> <item> <key>HlrFtpPutCopyDir</key> <value>C:\DevPath2</value> <encrypted>False</encrypted> </item> .... </Provisioning.Lib.Processing