teamcity-7.1

I am trying to run msbuild with teamcity. I have a batch file and I pass into it parameters and the build works. When I try to run through teamcity I get error below [13:24:46][MSBuild output] Start MSBuild... [13:24:46][MSBuild output] 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe' '"@C:\TeamCity\buildAgent\work\999585556854a516\Build\Default.msbuild.teamcity.msbuild.tcargs" C:\TeamCity\buildAgent\work\999585556854a516\Build\Default.msbuild.teamcity' [13:24:46][MSBuild output] working dir = 'C:\TeamCity\buildAgent\work\999585556854a516' [13:24:46][MSBuild output] Microsoft (R)

I don't want Build Config A and Build Config B to run at the same time. This is because they share the same resource which cannot be accessed simultaneously. However each build config is run by a separate agent so it is possible for them to run simultaneously. Instead I would like one build config, when triggered, to wait for the other to finish if it is running. For example if Build Config B begins to run but Build Config A is already running, then B would wait until A finishes and then B would run. I don't think a snapshot dependency will work because that assumes one config has a dependency

How to get the changes of a teamcity build? I got the following URL wich list all the build changes and provides a URL using which we can view the changes http://teamcityserver/httpAuth/app/rest/changes?buildType=id:bt2 However the given URL "/httpAuth/app/rest/changes/id:433" takes the id which is modification id. How do we get the modification ID? Can we pass the internal build ID or number to get the chnages of a specific build? Perhaphs what you need is this: " https://teamcity.blabla.com/httpAuth/app/rest/changes/buildType:(id:20140010),build:(number:102) " (yes it has a comma in there)

I receive the following error in NuGet Install build step when setting sources to TeamCity's NuGet server: Step 1/4: NuGet install (NuGet Installer) (3s) [15:11:19][Step 1/4] scan: Searching for nuget.config files [15:11:19][Step 1/4] install: Installing NuGet packages for packages.config (3s) [15:11:19][install] NuGet command: C:\TeamCity\buildAgent\tools\NuGet.CommandLine.2.2.0.nupkg\tools\NuGet.exe install C:\TeamCity\buildAgent\work\a4b9de5be22a981\packages.config -OutputDirectory C:\TeamCity\buildAgent\work\a4b9de5be22a981\packages -Source http://localhost:9090/guestAuth/app/nuget/v1

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

I have the following set-up in TeamCity 7.1.3: Project A Build & Deploy A Test A (Quick) Test A (Slow) Test A (Very Slow) Project B Build & Deploy B Test B (Quick) Test B (Slow) All of the tests for A depend on 'Build & Deploy A' and all of the tests for B depend on 'Build & Deploy B'. The dependencies are all snapshot dependencies with the following settings: Do not run new build if there is a suitable one Only use successful builds from suitable ones Run build on the same agent All of the tests have VCS triggers. The slow tests only run when particular folders in source control are changed.

I have one TeamCity project Dac.Test that contains 3 configurations: DEV , QA , PROD . Also I have some users associated with their Roles. Is this possible to hide / show certains configurations for selected users or groups? For example: Users associated with group: Testers can see QA configuration, but not PROD and DEV . There is no way of managing user permissions per-build, this is available on a project level only. You could create a sub-project in the Dac.Test project to cater for this If you're looking for a way of stopping people from mistakenly running this build, the following