Jenkins vs. TeamCity
As of July 2019, Jenkins is ranked 1st in Build Automation with 14 reviews vs TeamCity which is ranked 3rd in Build Automation with 6 reviews. The top reviewer of Jenkins writes "Significantly reduces build times, automates frequent manual tasks, reduces errors". The top reviewer of TeamCity writes "The flexibility of the product allows it to support a seemingly infinite number of build workflows". Jenkins is most compared with TeamCity, CloudBees and GoCD. TeamCity is most compared with Jenkins, GitLab and Bamboo. See our Jenkins vs. TeamCity report.
Most Helpful Review | |||||
|
| ||||
 Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: July 2019. 352,354 professionals have used our research since 2012. | |||||
Quotes From Members
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
Pros | |
This solution has helped us in automating the build and test process, reducing time. It is very useful for us to be able to collect and manage automatic processing pipelines. The most valuable feature is its ability to connect with different tools and technologies. There are a large number of plugins available for integration with third party systems. Having builds and test tasks triggered on commit helps not to break the product. We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity. We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable. Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead. | I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC. The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine. It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack. Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end. It's easy to move to a new release because of templates and meta-runners, and agent pooling. VCS Trigger: Provides excellent source control support. Good integration with IDE and JetBrains products. |
Cons | |
The upgrades need improvement. The learning curve is quite steep at the moment. This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager). The user interface could be updated a little. Jenkins relies on the old version of interface for configuration management. This needs improvement. Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things. Sometimes you have Jenkins restarting because of OOM errors. Centralized user management would be helpful. | Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone) to provide training classes to help newcomers get things up and running more quickly. It will benefit this solution if they keep up to date with other CI/CD systems out there. Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted. REST API support lacks many features in customization of builds, jobs, and settings. The upgrade process could be smoother. Upgrading major versions can often cause some pain. I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does. |
Pricing and Cost Advice | |
Jenkins is open source and free. I used the free OSS version all the time. It was enough for all my needs. Some of the add-ons are too expensive. It's free software with a big community behind it, which is very good. It is free. Jenkins is open source. It is a free product. | Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most. |
Find out what your peers are saying about Jenkins vs. TeamCity and other solutions. Updated: July 2019.
352,354 professionals have used our research since 2012.
See also Jenkins Reviews, TeamCity Reviews, and our list of Best Build Automation Companies.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post
reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference
with LinkedIn, and personal follow-up with the reviewer when necessary.
Sign in to see all reviews and comparisons. It's free!
By clicking Sign in with LinkedIn™ you agree to let IT Central Station use your LinkedIn profile
and email address in accordance with our Privacy Policy and agree to the Terms of Service.
- Unlimited access to 27000+ reviews from real users
- Your own page to promote your professional skills
- Networking events and peer-to-peer consultations
Already a member? Sign in.
By registering, you agree to our Terms of Service and Privacy Policy.
- Unlimited access to 27000+ reviews from real users
- Your own page to promote your professional skills
- Networking events and peer-to-peer consultations
Already a member? Sign In.