teamcity

I've created a Team City build to build the feature branches: Default Branch: refs/heads/development Branch Specification: refs/heads/feature/* I have a vcs trigger so it builds for every git push. But I don't want it to build when someone pushes to the development branch. I have tried playing with the branch filter in the trigger, but either features and development build on push, or none of them do. I'm using TC 9.1.1 Alina Mishina Try the following settings: Default Branch: refs/heads/development Branch Specification: +:refs/heads/feature/* VCS trigger branch filter: +:* -:<default> We are

We use UI Automation and Nunit to create tests UI tests for WPF application. We've created tests that work fine when you run them from a local machine. Those tests never run successfully on our build server (using TeamCity). Build always hang after opening application window. But if I am logged in (remote desktop), on our build server all UI Automation tests also run successfully. So I am guessing that it probably has something to do with running active windows session. Any ideas how to convince our build server to create active windows session or any other solutions for making those tests run

Is it possible to Trigger an exe to run on a failed build? Can you do this within Team City? If you specifically want the failed builds, you can set up the dependent build as Eric said, and have that secondary buildscript use the REST API to pull up a list of the failed builds for the actual project. If the latest build is in that failed builds list, then tell the build script to run the executable. If not, then you're all done! http://confluence.jetbrains.net/display/TW/REST+API+Plugin I don't think it's possible to trigger an executable to run only on failed TeamCity builds. TeamCity usually

I am using TeamCity and I am new to it. I have added a Build Configuration to the TeamCity and I created one VCS root to attach to it. However, my project have a special requirement to detect a particular file that was changed in the VCS root location and use that file in build step. I am sure this could be done in TeamCity, I am not able to figure out how. Any help? Thanks, To get the names of the files changed this is what I did. Thanks to Sam Jones. I used System.TeamCity.build.changedFiles.file variable as follows. Add a command line build step Select Run as Custom Script Add the script

I'm new to Continuous Integration. I want an advice with what tool should I start deal with. I see that this is the biggest tools right now: CruiseControl.NET, TeamCity and Visual Studio Team System. I'm using this tools: Visual Studio 2010, Mercurial, NAnt, NUnit. Both TeamCity and CruiseControl.NET will work fine for this set of tools. Also you can consider alternatives : Hudson (Free, UI-based setup) Visual Studio Team System (expensive (about 6000$), UI-based setup) CruiseControl.NET (Free, Xml-based setup) TeamCity (Professional Edition of TeamCity is free, UI-based setup) The difference

I recently re-configured our TeamCity build configuration to take advantage of the Branch features to apply the same build configuration to multiple branches in the same repository. Now, I'm trying to setup an automated build script that can pull the latest artifact from TeamCity, but only for a specific branch. I was able to get it working fine on the default branch in the original configuration, using the TeamCity REST API, but can't figure out how to format the URL to pull the artifact for a specific branch. I've looked at the following resources, but to no avail: http://confluence

I have a TeamCity agent configured to build my XCode projects and I use github. I would like to automatically include in my release notes the descriptions from all pending commits in TeamCity. How can I fetch them from github and store them in teamcity? Once I put them in a teamcity variable I can easily add them to my build script. VonC You could use the " Adding or Changing a Build Parameter from a Build Step " feature in order to update some build parameters right from a build step. You would need a step which would call git log origin/master..master (see " git: list commits not pushed to