TeamCity Reviews

We use TeamCity for build configuration and pipeline creation, as well as for automation purposes. We provide working pipelines for different teams internally.

We can use multiple types of agents, like Linux-based and Windows-based, which supports all types of languages in scripting when we mention a build step.

We use it for running unit tests for merge requests on github. We also use it to build executable artifacts and also for running security scans.

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.

We use TeamCity for the CI/CD pipeline. It is used for deploying code from the desktop to the production environment. We push our code to GitHub, which then creates a pipeline to a server using AWS, deploying automatically without errors or conflicts in GitHub branches. 

We also use TeamCity's version controlling for our staging, production, and development environments.

TeamCity has significantly streamlined our deployment processes, allowing for a straightforward and quick path from code development to deployment. By automatically warning us of outdated libraries or errors during the upload, it helps maintain a high standard of code quality and ensures smooth deployments.

I used the product to deploy changes to UAT for testing and then to production.

The integration between Bitbucket and TeamCity could be smoother. I encountered challenges when passing data from Visual Studio to Bitbucket and TeamCity. Improved documentation or out-of-the-box connectors enhance this process.

We integrate TeamCity with Git for our development process. After the integration, we set up commands using web method integration to allow users to create builds and perform other tasks. These builds are then deployed on our internal servers.

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. 

We have different projects on TeamCity. Mainly, for example, I use it to automate our build. We have scripts that need to be run on schedule to do some scanning of our codes to detect vulnerabilities and so on. I have, for example, a build that decorates the script and launches it every Sunday night, so we can have our reports by Monday, so our managers can see them, and we can discuss them.

We also use it to deploy our infrastructure as code in the environment and to execute that or deploy that to the dev environment. We have many builds that deploy our code in the dev environment.

TeamCity is a very user-friendly tool. I didn't know about it five months ago, and I started digging into it. To be honest, it was very easy to start on it and to build my first build and to understand the concept or the methodology internally. 

It's very easy to configure as well. You can configure your build and the steps within in it in a very easy way since you can choose the syntax with how you will write your code. In comparison with Gitlab, Gitlab has its specific syntax, so you need to learn that; however, with TeamCity, you have the choice to choose the framework you want and so you can start easily. 

Creating build environments for a various range of embedded (C/C++) products with multiple build agent configurations. Empowering the integration team (verification testing) with the ability to test subsystems of applications before launch.

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.

For my company, we require a CI server that's very flexible. Our bills are simple, almost template-based, however, we need to be able to deploy to almost any platform, basically whatever the customer could end up using, whether it be Windows, Mac, Android, and even mobile or tablets, et cetera. We can do it with this solution. 

It needs to be simple because right now as I am the only IT person knowledgable of infrastructure on the team. If we need to build a pipeline, it needs to be simple enough that the rest of the team would be able to understand and work with it.

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.