teamcity

Is it possible to pin a build in Teamcity programmatically/automatically? I want to pin a build if a Deploy-build is successfull. Just found out that its possible through the REST API I can f.ex send a PUT command like this http://teamcityserver:81/httpAuth/app/rest/builds/id:688/pin/ and then the build with id 688 ( teamcity.build.id ) will be pinned. I would like to challenge the accepted answer with an up-to-date answer, which was tested with TeamCity 9 EAP 4 (build 31717) and 8.1.x. Tagging and pinning could be implemented via a simple plugin that contains just an event adapter such as the

I'm trying to set up a new build configuration in TeamCity using the Powershell runner. However, I can't seem to find a way to access the TeamCity System Properties in the build script. I've seen hints that it is possible, but cannot find documentation on how to do it. I have tried accessing the system properties using Powershell variable syntax, $variable. I have also printed out all variables in memory and see no teamcity variables to use. Is this possible with the Powershell runner, and if so what is the syntax necessary to get it working? TeamCity will set up environment variables, such as

I want to create create a label (tag) in the SVN with a file's version. I'm already renaming the artifact by getting the file version of the main executable produced by the build. Such as: MyInstaller-1.2.3.1.exe . Now I want to create a tag in the SVN called /tags/1.2.3.1 . I couldn't find a way to set such a thing in the labeling pattern. Currently my labeling is just "%system.build.number%" Any idea about how to do this? I'm using TeamCity Professional Version 4.5.3 (build 9035) As someone mentioned, you can output the build number during the execution of the build script, and teamcity will

We have over 150 projects which I have gathered together, reconfigured and optimised into multiple TeamCity configurations, with multiple build agents, to try to improve our build server performance which currently builds in a highly sequential manner. The mix of technologies (Web, dotNet, VB6 and COM+) and system architecture means that there are various steps (configurations) which can now run in parallel but which need to come together further down the track. This is a very simplified dependency scenario but representative of a problem we have.... A -> B -> Collate (-> Deploy) A -> C ->

We are using Teamcity to do continuous integration builds for our website and have just upgraded our website to .Net 4.5RC. The application builds and runs in IIS express on my box and builds on our build server that I have installed .NEt 4.5RC on. But when we deploy it to the server that has had .Net 4.5RC installed on it we get the following error. The application pool that you are trying to use has the 'managedRuntimeVersion' property set to 'v4.0'. This application requires 'v4.5'. What can I do to fix this problem. I have tried setting the application pool on the server to 4.5, but can't.

I have a TeamCity build configuration that has been working fine until recently. Suddenly, there is a build stuck in the queue that says it is not compatible with any agents. The reason given is: Implicit requirements: teamcity.build.branch defined in Parameter: BuildFormatSpecification My BuildFormatSpecification parameter is defined thus: %MajorVersion%.%MinorVersion%.%PatchVersion%-%teamcity.build.branch% That in turn is used in the Build Number Format field along with a build counter, like this: %BuildFormatSpecification%.%sharedBuildNumber.id4% The idea is that the build number comes out