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."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."
"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's GUI is nice."
"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."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The integration is a valuable feature."
"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 flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"They could work on reducing the number of permissions required while using Bitbucket."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"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."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
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.