Item: TeamCity
Rating: 9
Author: Verified User

Overall Satisfaction with TeamCity

Use Cases and Deployment Scope

We make use of TeamCity to build and deploy our code from our git repositories to our various environments - development, test, staging, and production. We have incorporated comprehensive tests into the process as well, making TeamCity the backbone of our CI/CD pipeline that has strengthened our ability to deliver features.

Pros and Cons

Pros

The ability to have different build processes and monitoring per branch/environment
Run tests as part of the CI/CD pipeline
Status monitoring across multiple projects with build histories

Cons

When it is time to upgrade versions it is a cumbersome and time consuming process
Some of the reporting could be better, no real visualizations of pipelines, histories, etc.

Most Important Features

Separate build processes per branch/environment
Easily incorporate tests
One click build and deployment

Return on Investment

Allowed us to set up stable and robust CI/CD pipelines to deliver features more frequently with less bugs
Easy integration with other JetBrains tools that were already in use limited setup time and future products can be added quickly

Alternatives Considered

Jenkins

Since we were already making use of other JetBrains offerings, TeamCity had a leg up on the competition due to the ease of integration with these tools. With that said, TeamCity's feature set stacks up well with the competition. Jenkins definitely has some nice features, but TeamCity meets all of our needs and performs very well.

Key Insights

Do you think TeamCity delivers good value for the price?

Yes

Are you happy with TeamCity's feature set?

Yes

Did TeamCity live up to sales and marketing promises?

Yes

Did implementation of TeamCity go as expected?

Yes

Would you buy TeamCity again?

Yes

Other Software Used

Jira Software, Atlassian Confluence, Jira Service Management (Jira Service Desk)

Likelihood to Recommend

TeamCity is well suiting for building and maintaining CI/CD pipelines across multiple branches and environments where each one can have unique build processes and steps. It is straightforward to incorporate tests into the process as well. Generally speaking, it performs well and scales with the business. If you are working with a simple, single project in one environment though you might want to look elsewhere as I think TeamCity might be overkill for your needs.

Comments

Please log in to join the conversation

TeamCity Delivers