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."With Jenkins, the pipeline will take your code from any versioning system like GitHub or Bitbucket. All the security scans can happen in one go and then all the tests also get run. You can just build one container in it and deploy it."
"The solution is scalable and concurrent users have access to the platform."
"Jenkins is very user-friendly."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"Jenkins has been instrumental in automating our build and deployment processes."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"Good integration with IDE and JetBrains products."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"The integration is a valuable feature."
"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."
"TeamCity is a very user-friendly tool."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"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."
"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"The solution's UI can use a facelift and the logs can use more detailed information."
"A more user-friendly UI for creating pipelines would be helpful."
"It would be better if there were an option to remove its Java dependency. This would make it more compatible with other software, and it could be much better. At present, we have to depend on Java whenever we want to deploy agents."
"We cannot change the ownership of any directory or file or any kind of directory."
"I need some more graphical design."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"If there was more documentation that was easier to locate, it would be helpful for users."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
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 Digital.ai Release , whereas TeamCity is most compared with GitLab, CircleCI, Harness, GitHub Actions 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.