2018-03-20T14:54:00Z

What is your primary use case for TeamCity?

Miriam Tover - PeerSpot reviewer
  • 0
  • 4
PeerSpot user
Get the report
Helped 765,234 peers since 2012
7

7 Answers

MW
Real User
Top 5
2022-09-07T15:37:23Z
Sep 7, 2022

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.

Search for a product comparison
Omakoji Idakwoji - PeerSpot reviewer
Real User
Top 20
2022-06-27T19:07:36Z
Jun 27, 2022

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.

SS
Real User
2021-10-22T20:26:43Z
Oct 22, 2021

We generally use TeamCity for automation and development.

TS
Real User
2020-07-02T10:05:58Z
Jul 2, 2020

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.

RR
Real User
2019-12-16T08:14:00Z
Dec 16, 2019

We primarily use the solution for application building and testing, continuous integration testing, and continuous delivery.

AM
Real User
2019-05-07T15:57:00Z
May 7, 2019

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.

Learn what your peers think about TeamCity. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
SG
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.
Download TeamCity ReportRead more