teamcity

I recenlty updated my TeamCity to the newest Version. (10.0 build 42002) Since then the build agent can't build any of my projects. The agent tells me the following: Unmet requirements: DotNetFramework4.0_x86 exists To solve this problem I already did what was suggested in this stackoverflow question: TeamCity Agent Missing DotNetFramework4.0_x86, but not? Sadly it doesn't work. So I looked at the log files but didn't find anything weird. Then I looked at the agent configuration paramets. I found this: DotNetFramework4.6.01055_x64_Path C:\Windows\Microsoft.NET\Framework64\v4.0.30319

Is it possible to format powershell output so that it renders as a collapsible section in the TeamCity build log, Tree view? So for example, my build step uses a powershell runner, and issues a write-host " ################# deployment manifest ############################" ls -r -i *.* | %{ $_.FullName } which outputs this: [15:28:13] ################# deployment manifest ############################ [15:28:13]\\10.10.10.49\d$\sites\account.foo.net\v32\Bin [15:28:13]\\10.10.10.49\d$\sites\account.foo.net\v32\contact [15:28:13]\\10.10.10.49\d$\sites\account.foo.net\v32\Content [15:28:13]\\10

Is there a way to define teamcity['build.number'] property from command line? I tried -Pteamcity.build.number=1 but it didn't work. I have a build.gradle file with this task in it: distTar { baseName = project.name+'.'+ project.version+'.'+ System.getProperty("system.rnf.brach_name")+'.'+ teamcity['build.number']+'.'+ teamcity['build.vcs.number.1'] archiveName = baseName+'.tar' into(baseName) { from '.' include 'config/*' include 'run-script/*.sh' } } It works on the build server, but it drives all the developers crazy, because we don't have teamcity installed on our machines, and any gradle

In the spirit of keeping my SVN trunk clean and ready for deployment, I've been utilizing the following source control model . For the impatient, the basic concept is that you create development branches to do actual development, and leave the trunk clean and ready for deployment, at any time (no junk in the trunk). In addition to this, I am configuring TeamCity for continuous integration. Within TeamCity, I'd like to ensure that all development branches, as well as the deployment-ready branch (the trunk, in my case) build correctly and pass all unit tests. This might be a stupid question, but

I'm trying to put branch name into build number, but I can't find the right parameter. I'm using build number format : %teamcity.build.branch%.{0} It works, but when it trying to build default branch 'dev', teamcity names it as <default> . How to fix it ? I was able to solve this problem by: In my VCS Root - using git - set my Default Branch to: master In my VCS Root - using git - set my Branch Specification to: +:refs/heads/(master) +:refs/heads/(release-*) +:refs/heads/(hotfix-*) Create a Configuration Paramater: BuildNumberPrefix = SomeService.%teamcity.build.branch%.release_ Set my Build

I have several projects that produce NuGet packages that I publish to an internal server. We're using semantic versioning , and using tags in our Git repository to control the version numbers. I'm tagging like this: git tag -a v1.0.0 -m "tagged" And, during the TeamCity build, I run git describe --long , which produces an output like this: v1.0.0-0-ge9c047d The fourth number in the output is the number of commits after the tag. The 0 here means that no commits have been made since the tag. I use these first four numbers as the version number (and, incidentally, the entire string as the