TeamCity Review

Templates, meta-runners, and agent pooling make it easy to move to a new release


What is most valuable?

  • Templates
  • Meta-runners
  • Plugins
  • Multiple version control system support
  • REST API support

How has it helped my organization?

We can build our code daily and automatically, with email notification for failures. It's easy to move to a new release because of templates and meta-runners, and agent pooling.

What needs improvement?

REST API support lacks many features in customization of builds, jobs, and settings. 

Also, integration with newer technologies needs improvement.

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

Depends on the server host, but it runs on Java so it needs high specs. Otherwise, the website takes a long time to load. 

Also, supporting newer technologies is limited.

What do I think about the scalability of the solution?

You have to clean up old projects, otherwise the load on the server increases with increase in size of projects.

How are customer service and technical support?

Technical support is good.

Which solution did I use previously and why did I switch?

No previous solution.

How was the initial setup?

Straightforward, the documentation on the website is very helpful.

What's my experience with pricing, setup cost, and licensing?

I don't handle pricing so I can't really advise on this.

Which other solutions did I evaluate?

We did not evaluate other options but we may consider moving to Jenkins because it's free and has many similar features.

What other advice do I have?

Use Templates and meta-runners, they are very useful in scaling your product with new releases.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email