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, Amazon Web Services (AWS) and others in Build Automation."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."
"The platform has some amazing features and the integration option makes it very simple to plug with any of our favorite tools."
"VCS Trigger: Provides excellent source control support."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"The integration is a valuable feature."
"TeamCity's GUI is nice."
"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."
"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."
"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."
"They could work on reducing the number of permissions required while using Bitbucket."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"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."
"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 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."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
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, Harness, Bamboo and GitHub Actions, whereas TeamCity is most compared with GitLab, CircleCI, Jenkins and GitHub Actions.
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.
