We performed a comparison between JFrog Pipeline and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"Testing against multiple run times, versions, and environments is a plus point with the additional pipelines making it more interesting to see what is happening across your development process in a single pane of glass."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"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."
"The integration is a valuable feature."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity's GUI is nice."
"Good integration with IDE and JetBrains products."
"They could work on reducing the number of permissions required while using Bitbucket."
"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."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
"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."
"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
Earn 20 points
JFrog Pipeline is ranked 22nd in Build Automation while TeamCity is ranked 6th in Build Automation with 25 reviews. JFrog Pipeline is rated 8.0, while TeamCity is rated 8.2. The top reviewer of JFrog Pipeline writes "Testing against multiple run times, versions, and environments is a plus point". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". JFrog Pipeline is most compared with Jenkins, Bamboo, Harness and GitHub Actions, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and Concourse for VMware Tanzu.
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.