teamcity

How can I override the <default> branch name in TeamCity 7.1 using Git branching support?

北城余情 提交于 2019-12-04 16:05:30
问题 I've got a CI build pulling feature branches from Github and building/packaging them into a local folder, using a folder naming convention based on the project, branch and build number. For named branches (feature1, feature2) this is working great. The problem is that when I do a commit to the master, TeamCity exposes teamcity.build.branch as <default> - which means when the build step expands E:\Packages\MyProject\%teamcity.build.branch%\ it's ending up with E:\Packages\MyProject\<default> -

Setting Teamcity version number with counter from file

China☆狼群 提交于 2019-12-04 15:41:57
I'm currently trying to update the version no. in TeamCity using a Nant build file, containing the version number. If I just use <property name="versionNo" value="2.16.3."/> . . <echo message="##teamcity[buildNumber '${versionNo}']"></echo> In the script the buildNumber is update to 2.16.3 but I would also like to have the counter on this version number. Meaning I would like to have <echo message="##teamcity[buildNumber '${versionNo}.{0}']"></echo> But this doesn't work. Does anybody know how to do this, tried many things among this solution http://binary-notes.blogspot.com/2011/05/controlling

How can I run all NUnit Tests in Team City?

≯℡__Kan透↙ 提交于 2019-12-04 15:27:50
问题 We are using TeamCity 6.0 to build VS C# solutions each commit. Once the build is complete, a different test TC project runs. So that developers can add/remove/edit VS unit test projects, how can I make TeamCity use the the sln file or search for test dll's? I don't want to have to edit the build each time a new test project is added to the VS solution. Run tests from: **\*Test*.dll Doesn't appear to work, it only get s the first Test (which is currently failing) 回答1: Fixed :) - RTFL (Read

TeamCity command line build runner: How to make the build fail?

非 Y 不嫁゛ 提交于 2019-12-04 15:15:49
问题 We're using TeamCity's command line build runner to call a bat-file. The bat-file builds our solution by calling the Visual Studio 2008's "devenv.exe" and then it executes the unit tests and creates the correct folder structure. What we would like to do is to stop executing the bat-file if the call to devenv fails and make the TeamCity to realize that the build failed. We can catch the failed devenv call by checking the ErrorLevel (which is 1 if the build failed) and we can exit our bat-file

Nuget Restore via build server “unable to find version”

吃可爱长大的小学妹 提交于 2019-12-04 15:02:19
问题 I have a VS solution and as part of a TeamCity Build, we restore packages from both a private NuGet feed (myget) and the public feed (nuget.org). Most packages restore fine, but it hangs on the ones below for WebApi and Mono.Security. This is all working locally in Visual Studio. [restore] NuGet command: C:\TeamCity\buildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe C:\TeamCity\buildAgent\tools\NuGet.CommandLine.DEFAULT.nupkg\tools\NuGet.exe restore C:\TeamCity\buildAgent

web.config transformation does not work on build server

馋奶兔 提交于 2019-12-04 14:49:00
We are setting up continuous integration with team city doing builds on check-ins. This works fine, however it always builds with default web.config, it does not transform with development environment specific web config. In Visual Studio, I have custom build configuration created for development. The 'web.development.config' transforms correctly when I publish locally with 'development' configuration selected. But this does not happen on the build server. In team city, as part of msbuild step I have created a build parameter 'sys.configuration' and i am passing 'development' as the value. But

How can I generate a custom build number in TeamCity and then patch it to assembly info?

孤人 提交于 2019-12-04 14:44:39
问题 I have done some searching on this topic and am able to find individual solutions to generate custom build numbers as well as patch assembly info, however I am unable to accomplish both. When using a custom POWERSHELL script that I found in a search, I am able to set the build number to what I create with the script, however this build number does not patch. The only success I have in patching is when using set numbers plus a counter. But the number that the POWERSHELL script creates does not

fatal error: 'Fabric/Fabric.h' file not found

天大地大妈咪最大 提交于 2019-12-04 14:41:24
I am working on xcode 6.3.1, OSX 10.10.3 and I have configure crashlytics successfully with my local system. it work fine and it release the build via fabric app. But when I transfer same codebase to teamcity it was showing me following error fatal error: 'Fabric/Fabric.h' file not found fatal error: 'Crashlytics/Crashlytics.h' file not found After investigation, I found that following unknown issue in my teamcity server. Teamcity got the source from git and when I see the source code in teamcity, Crashlytics.framworks & fabric.framworks are available but when you look into folder structure it

How can I pass MSDeploy-style parameters to MSBuild via the commandline?

风格不统一 提交于 2019-12-04 14:29:20
I am setting up TeamCity to deploy our Website Project application (using a *.wdproj) and Web Deploy application to IIS. I have a build configuration that uses MSBuild.exe with the MSDeployPublish to build and then deploy the application. We now want to get the application to deploy to multiple target environments, therefore need a way to supply different settings based on the target environment. I have added a parameters.xml file to the Web Deployment Project, and have verified that the parameters set in here are making all the way through the target IIS server and being correctly applied -

Why does the TeamCity command line runner execute under “System”?

岁酱吖の 提交于 2019-12-04 14:06:59
I've got a bit of an auth problem with with TeamCity when running a command line build. It's related to an existing question about executing an svn checkout command but I want to ask it explicitly here: Why is it that when the TeamCity build agent service is configured to run under a specific Active Directory account and not the local system account, when I execute this command: echo "%username%" I get this build output: [20:52:04]: C:\TeamCity\buildAgent\work\b67560ceb299718c>echo "SYSTEM" [20:52:04]: "SYSTEM" This is really playing havoc with my attempts to execute commands under the