teamcity

Since GitLab 7.6, or thereabouts, there is a new option to use TeamCity directly from GitLab projects. In the setup there is this message: The build configuration in Teamcity must use the build format number %build.vcs.number% you will also want to configure monitoring of all branches so merge requests build, that setting is in the vsc root advanced settings. I'm not sure how this works. Lets say I have a repository Foo. I have setup a build on TeamCity to listen to Foo with branch specification: +:refs/pull/*/merge I then fork Foo in gitlab as FooFork, make a change, then request a merge

The default path for teamcity artifacts is C:\#User#\.BuildServer\system\artifacts How can i change it to d:\TeamCity\Artifacts Thanks For me the default is D:\BuildServer\system\artifacts Yes you can, set the TEAMCITY_DATA_PATH environment variable. See here: http://www.jetbrains.net/confluence/display/TCD4/TeamCity+Data+Directory By default, the is placed in the user's home directory (e.g. it is $HOME/.BuildServer under Linux and C:\Documents and Settings\.BuildServer) under Windows. Alternatively, you can define this directory in one of the following ways: As a Tomcat system property

Is it possible, without disabling all other connected agents, to force TeamCity to build on a specific agents machine? Jim Geurts Under Build Configuration Settings go to Agent Requirements and set an Explicit Requirement for the specific agent name: Parameter Name: system.agent.name Condition: equals Value: YOUR_SPECIFIC_AGENT_NAME For one time run you can click on the 3 dots next to "Run" and define on what agent you want to run. For a long term configuration you should use the Agent Requirements of the build. You can add a system property to the agent by editing the file ...\buildAgent\conf

As this was not answered (Maybe did I not find it) previously, I investigated on the following question : How to perform automated functional tests on Android devices with robotium, and report them to continuous integration server like TeamCity? As I did not find any answer on that specific question, I investigated. Here is the output of my investigation and a quick How-To in order to help people perform automated functional tests on Android applications using robotium, and then report the results to a continuous integration server like TeamCity. Please note that this may not be the best

How do I run MSTest as part of my build process in TeamCity? What are the pitfalls? 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\MSTest\testResults.trx Pitfalls Using wildcards when specifying which test assemblies to run You can use

I'm trying to get PartCover reports to generate correctly in TeamCity 5.0. When I click the Code Coverage tab in the build details, the reports are empty. I'm using the sln2008 build agent and my PartCoverage settings are as follows: Include Patterns: [*]* Report XSLT: C:\Program Files\PartCover .NET 2.3\xslt\Report By Assembly.xslt=>ByAssembly.html C:\Program Files\PartCover .NET 2.3\xslt\Report By Class.xslt=>ByClass.html Bonus points if you can describe how to include those reports (or just the important parts) with the email that TeamCity sends for successful/failed builds. I would like to

I'm trying to integrate the sonar analysis into by TeamCity build process. I have a NUnit build step which runs my unit tests and then runs dotCover for the coverage. My next step is the sonar-runner. The configuration that currently exists is; gallio.mode=dotCover, sonar.gallio.mode=reuseReport but I also need sonar.gallio.reports.path. Does anybody know the path to the dotCover report generated in the the previous step? I couldn't find a way to do this using the built in NUnit runner. I managed to get it working by using a powershell build step to manually call the required commands. First

Right now our assemblies have a version number like 2.0.831.0. As I understand it, that's major version, minor version, date and build number. If I make a change and build again on the same day it's 2.0.831.1, 2.0.831.2 etc. My TeamCity build number format is simply 2.{0} where {0} is an auto incremented number that just goes on forever (2.195, 2.196 etc). How do I make TeamCity look exactly like the assembly version? We want to be able to associate the Change Log with the assembly version so anyone can say assembly version 2.0.831.2 had these changes in these files. Extra info: Our build step

There are many sites that explain how to run signtool.exe on a .pfx certificate file, which boil down to: signtool.exe sign /f mycert.pfx /p mypassword /t http://timestamp.server.com \ /d "My description" file1.exe file2.exe I have a continuous integration CI process setup (using TeamCity) which like most CI processes, does everything: checks out source, compiles, signs all .exes, packages into an installer, and signs the installer .exe. There are currently 3 build agents, running identical VMs, and any of them can run this process. Insecure implementation To accomplish this today, I do a

I have created a new application using Entity Framework 4.3 database migrations. The migrations work great from the package manager console using the "update-database" command. Now I want to run the database migrations every time the application is built using Team City, it looks like I need to create a powershell script that will do this. Can anyone point me to some instructions on how to get the package manager commands to run from the command line, or powershell? All I can find is instructions on how to do this via the package manager console, which I don't know how to run from a Team City