We performed a comparison between Jenkins and TeamCity based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is very useful for us to be able to collect and manage automatic processing pipelines."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Jenkins is very user-friendly."
"Jenkins has built good plugins and has a good security platform."
"Jenkins is very easy to use."
"A lot of support material exists via a single web search of exactly what you're looking for."
"It has a lot of community posts and support."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"VCS Trigger: Provides excellent source control support."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"Good integration with IDE and JetBrains products."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"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."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"The UI of Jenkins could improve."
"The solution could improve by having more advanced integrations."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"It does not have a very user-friendly interface."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."
"This solution would be improved with the inclusion of an Artifactory (Universal artifact repository manager)."
"Better and easy-to-use integration with Docker would be an improvement."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"I need some more graphical design."
"If there was more documentation that was easier to locate, it would be helpful for users."
"REST API support lacks many features in customization of builds, jobs, and settings."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
Jenkins is ranked 2nd in Build Automation with 83 reviews while TeamCity is ranked 6th in Build Automation with 25 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.2. The top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, IBM Rational Build Forge and AWS CodeBuild, whereas TeamCity is most compared with GitLab, CircleCI, GitHub Actions, Harness and Tekton. See our Jenkins vs. TeamCity report.
See our list of best Build Automation vendors.
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.