Time to deployment has been reduced. It has helped in preventing us from deploying breaking changes into production. If the pipelines are configured properly and a merge request is created on the repository, the TeamCity pipeline triggers and highlights if there are breaking changes or failing unit tests. This has helped us reduce error rates immensely.

The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine. As we learn how to configure the build processes to fit our needs, it will prove to be a significant time saver.

The solution has been fantastic for our organization due to the fact that we do not need a designer having to build the product. We don't need to figure out how to deploy it either. It's created improved efficiencies which have saved us time and expense.  

It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack. This speeds up release cycles tremendously. Also, it helps when it comes to PCI/auditing (if set up correctly), as TeamCity has great security and tracking model.

It delegates the building of executable code to a machine.

• Improved the quality of builds by running unit tests as part of every build
• Reduced the risks of regression defects by running automated tests as part of the build process

• As a business we had a custom build process where the only people with access to the build were our build engineers.
• Teamcity allowed us to create a visual flow of the processes and steps involved in moving a build through its phases.
• The product also allowed us to identify areas for improvement in our process.

We've found that TeamCity has significantly improved our deployment process by automating tasks that were previously done manually. This automation has reduced deployment time and increased efficiency for our team. 

Continuous integration has reduced build failures and highlighted issues sooner. Automated deployments of web services, database scripts and applications chained across all environments has minimized time and effort, sped up delivery time, reduced risk of human error and enabled automated communication to stakeholders via integration with JIRA for release notes.

• Continuous deployment
• Continuous integration
• Testing feedback

Automatic VCS Triggers, MSTest, and NUnit integration made our workflow much faster and efficient. It just felt more mature and everything was working as we expected.

We used do all of our product development builds using .net and Java languages. It is very useful to setup build agents in a Unix platform for all kinds of Unix builds.

• Rerun failed tests after overnight execution, saving manual re-execution time during working hours.
• Run acceptance tests after each commit, giving quick and automatic feedback on software quality.
• Automate build pipeline process, removing human errors from the process itself.

TeamCity allows us to have self-sufficient development teams that can create their own builds and deployments. TeamCity has really allowed us to embrace continuous integration (even running full CI on all code branches with no extra effort).

Creating a meta-runner to use as a single build entry point. The templates allow a consistent configuration on how an application is built, and by combining the use of the meta-runner and build templates, the whole organisation understands, and follows, this convention. By following this convention, a complete build stack is completed in a single REST call.

It increases the visibility and clarity of build and deployment activities.

With Teamcity, our build/packaging process and the ensuing deployment via Octopus Deploy takes less than half an hour. We have a customer base of approximately 40,000, spread over hundreds of virtual machines, so a fast deployment with little to no downtime is critical.

Being the sole TDD developer in an organization is not enough if the rest of the team does not test as well. Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end.

We can build our code daily and automatically, with email notification for failures. It's easy to move to a new release because of templates and meta-runners, and agent pooling.

People react faster on failing builds.