We use TeamCity for build configuration and pipeline creation, as well as for automation purposes. We provide working pipelines for different teams internally.
WebMethods Developer at a hospitality company with 1,001-5,000 employees
Real User
Top 20
2024-04-12T07:26:00Z
Apr 12, 2024
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 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.
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.
I've used TeamCity for many years at three different companies. This has been mainly for CI -building and testing software, but also for CD - continuous delivery and deployment. This has included .NET, Java, Ruby on Rails applications, running database scripts, and basically doing anything that can be automated.
Lead Engineer at a healthcare company with 10,001+ employees
Real User
2018-03-20T14:54:00Z
Mar 20, 2018
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.
TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.
We use TeamCity for build configuration and pipeline creation, as well as for automation purposes. We provide working pipelines for different teams internally.
I used the product to deploy changes to UAT for testing and then to production.
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 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.
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.
We generally use TeamCity for automation and development.
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.
We primarily use the solution for application building and testing, continuous integration testing, and continuous delivery.
I've used TeamCity for many years at three different companies. This has been mainly for CI -building and testing software, but also for CD - continuous delivery and deployment. This has included .NET, Java, Ruby on Rails applications, running database scripts, and basically doing anything that can be automated.
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.