teamcity

问题 I have two agents that can build my configuration. I've set up two because I sometimes need to do two simultaneous builds. How can I set build agent priorities to force TeamCity choose specific agent if both are idle and available? Now it chooses agent randomly or by some unknown factors... 回答1: You can filter which agents are used but I'm not sure you can specify which idle to agent to use. If you are worried about TeamCity using the fastest agent it should do this automatically. The

问题 I have done a lot of googling but cant seem to find an exact solution to get the TeamCity build number into my AssemblyInfo files. Would appreciate a full solution for my requirements... 1 Get the build number into a Nant variable. I believe that this code will accomplish this.. PropertyGroup Version$(BUILD_NUMBER)/Version /PropertyGroup (repoduced as best as possible in SO). 2 Now I need a way to update the revision component of my version numbers so I get something like 1.0.0.[build number]

问题 What does it mean to have TeamCity build agent installed on another machine than the Build server? The way I understand is that I need "TeamCity server install" to start a "agent install" right? Right now I have TeamCity build server installed with webUI and all of that on a windows server machine. Now what do I need to do, to install an agent on another machine (another server machine?) 回答1: The teamcity documentation is really good. Check out the Installing Agents section. You can have a

问题 What does it mean to have TeamCity build agent installed on another machine than the Build server? The way I understand is that I need "TeamCity server install" to start a "agent install" right? Right now I have TeamCity build server installed with webUI and all of that on a windows server machine. Now what do I need to do, to install an agent on another machine (another server machine?) 回答1: The teamcity documentation is really good. Check out the Installing Agents section. You can have a

问题 I have configured a Nunit test runner build step which successfully runs my testsuite, pointing at a test sub-project of my .Net solution eg. Solution/Solution.Test/bin/debug/Solution.Test.dll. My solution structure is as follows: Solution Solution.Lib Solution.Model Solution.Test Lib and Model dlls are referenced in the test project. I then turned on dotCover without any assembly filters and it performed code coverage analysis on the above test dll correctly. I then added a filter, -

问题 I am currently setting the assembly version on all my C# assemblies using the TeamCity AssemblyInfo Patcher. The version scheme I chose is 'Major.Minor.%build.number%.0'. This works fine when I define Major and Minor numbers in TeamCity, but ideally I would like to have them already defined in my AssemblyInfo.cs file and have TeamCity only set the value for the build number. Is this possible? One solution I see is to forsake using AssemblyInfo Patcher and use my own version update script, but

问题 In TC there is a project with a couple build configurations. Build configs targets projects that not interfere with each other - so I can start the build process simultaneously. On each build configuration home page there is Run button that starts the build. My question - there is possible to create a such button that triggers the build of all configs? I know that there is Build triggers and so on - but sometime there is need to start all build configuration - "on demand" build run - and it

问题 I am using TeamCity to run an MSBuild script that cleans and rebuilds one of our solutions. When I deploy the dlls that are built by this process, the web server returns an error about [MyType].XmlSerializer.dll that "This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded." Here are my notes so far: The solution is a Visual Studio 2010 solution that is targeting the .Net Framework 3.5. TeamCity is set to mimic this. It is set up with MSBuild version -

问题 <TLDR> Running an MSTest test from the command line hangs without any errors or timeouts whilst "waiting for runs/agents". The reason might be that "there are no runs in the queue", but why this is so I have no idea, because the exact same test runs just fine on another machine. </TLDR> We've recently moved from evaluating TeamCity on a test machine, to installing it in our production environment. After migrating all of our build configurations we suddenly got problems with our MSTest tests:

问题 According to Pitest's documentation, it seems that this should be simple, but it is giving me some trouble. I should be able to have java -cp <your classpath> \ org.pitest.mutationtest.commandline.MutationCoverageReport \ --reportDir c:\\mutationReports \ --targetClasses example.foo.* \ --sourceDirs c:\\myProject\\src \ --targetTests example.foo* but I don't know what some of those things should be for my project, such as "<your classpath>". My project's file structure looks like this: