TrustRadius: an HG Insights company

TeamCity

Score7.4 out of 10

60 Reviews and Ratings

What is TeamCity?

TeamCity is a continuous integration server from Czeck company JetBrains.

TeamCity, a must for every team

Pros

  • User interface
  • CD
  • Pipeline

Cons

  • Updates
  • Customer service

Most Important Features

  • User interface
  • Stability
  • Security
  • Pipeline priority

Return on Investment

  • Reduced complexity
  • Reduced redundancy
  • Unified solution for all projects

Alternatives Considered

Jenkins

Other Software Used

DevExpress Universal, Visual Studio IDE, IBM Cloud App ID

TeamCity packs a mean punch for teams both big and small.

Use Cases and Deployment Scope

TeamCity is our primary build, test, and deploy automation tool. It is the key orchestration piece for the SDLC of more than 12 software products. TeamCity allows us to automate a number of tasks to ensure repeatable results and allows team members to spend more time developing rather than running through the manual work of testing and deploying our software solutions.

Pros

  • build automation.
  • Deployment automation.
  • unit test automation.
  • dependency chaining.
  • branch management.

Cons

  • The UI is getting a bit dated but has taken on a serious overhaul in recent builds.
  • Build configurations as code uses a push/pull mechanism which feels a bit clunky to use.

Most Important Features

  • Branch management and branch scoping of builds.
  • Simple .NET build configuration options.
  • Extremely powerful free tier.
  • Simple agent and server management.

Return on Investment

  • Huge improvement in test automation to allow us to find breaks faster.
  • Saves hours a week of developer time in deployment automation.
  • Helped eliminate manual errors in deployments.

Alternatives Considered

Jenkins and Azure DevOps Services

Other Software Used

LastPass for Business, Azure App Service, Sublime Text

TeamCity is an important part of our product pipeline

Pros

  • See build status across many projects.
  • It monitors multiple branches with different build processes for each.
  • It's a useful unit test runner with test history and identification of flaky or problematic tests.

Cons

  • Reading build output logs can be a pain at times, as they aren't really parsed; just long lines of output.
  • When you have multiple projects and branches, determining what is currently building, what is pending, and what has failed can be difficult.

Return on Investment

  • Tracking unit test history has identified problematic test and real bugs that would be difficult or impossible to detect manually.
  • It keeps our pipeline quick and slim, allowing us to focus on getting more features and bug fixes out without worrying about messing up builds and deploys.
  • Integration with other JetBrains products makes integrating other tools relatively painless.

TeamCity is the ideal tool for agile teams using continuous integration

Pros

  • TeamCity provides a great integration with git, especially Bitbucket.
  • When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
  • TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.

Cons

  • Upgrading TeamCity is a long and manual process.
  • Java skills are needed to fully utilize TeamCity, although they are not necessary for basic or medium-level use.

Return on Investment

  • TeamCity provides positive ROI by catching errors before code releases and providing helpful details about the errors.
  • TeamCity saves our developers time by automating the build process as much as possible.

Alternatives Considered

Microsoft Visual Studio Team System

Other Software Used

MS SharePoint, OneDrive, Parse.ly

TeamCity 7 Years On!

Pros

  • A very friendly UI with good drill-down and "Pro" capabilities compared to all other CI systems
  • A good reporting system that allows all our different types of automation tests to produce output for
  • Fantastically simple to setup and configure

Cons

  • The biggest and only issue we have is the lack of a SaaS-based TeamCity solution. Currently, we have to host and maintain 1 big TeamCity server and up to 15 build agents to build our 1500+ builds

Return on Investment

  • We were able to ensure we're deploying the correct version of each component with ease and assurity

Alternatives Considered

Jenkins and CircleCI

Other Software Used

CircleCI, Jenkins