TeamCity

We used TeamCity as our Core Continuous Integration solution for four years. I love TeamCity's easy to use interface, and the way builds and releases are linked together in dependency Chains. I found it particularly helpful that Builds can be run separately, or in advance of Releases - and then when Releases are run the Builds only run again if the code has changed. TeamCity's Templates, Variables, and Parameterization capabilities also made it very easy to establish a flexible template for common solutions such as deploying MVC applications to IIS. Once templates were configured I could create a "build and release" for a new project in less than 10 minutes.

While TeamCity has a simple to use and understand chaining mechanism, allowing builds to call "builds and releases" to rely on multiple dependency chains - TeamCity's PipeLine visualization capabilities are one of its weakest points. I had a complex build across five different environments consisting of eight different solutions and over 20 deployment targets. During a major update, it would have been nice to visualize the deployment pipeline and "watch" the deployment process for issues - but that really isn't possible with TeamCity. Outside of that, TeamCity worked great, integrated well with all of our platforms: Git, Azure, AWS, Visual Studio Team Services.

Great Product.

TeamCity was used by my team to do the continuous evaluation and integration of various projects under our team. It was used by our team only in our organisation. It was easy to spot wrong commits and build a failure before the product release. This was very easy with the help of a continuous integration tool like TeamCity that has a very versatile UI.

I set up TeamCity for our core product continuous integration. For both the main product and the core libraries it is used to compile on check in, build and deploy on pull requests, and to run the unit and functional tests. No code goes into the develop or main branches without passing through this process.

TeamCity is being used across my company. We have integrated TeamCity with the CI/CD pipeline. This is solving number of problems which occur if we do not have CI/CD in place. Configuring node servers to build the projects is easy. We can easily configure the properties while building the specific branch. Can easily build multiple feature/develop/release branches at once. It gives all build related information at one place, so can troubleshoot problem in build easily. Basic implementation of application is easy.

We use TeamCity for Continuous Integration & Delivery of our software products. We have many projects for various customers that are built and integrated continuously whenever we check code into our git repositories.

We use a mixture of Gradle & Maven builds and TeamCity handles both well.

We get immediate feedback from TeamCity if a code change has caused issues with other linked projects and, because we have confidence in our tests we also have confidence in a 'green' build prior to delivery to a customer.