We performed a comparison between IBM Rational Build Forge 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."All features are useful. Our customer doesn't have any complaints about the tool. It works pretty well for what they want and what they need to do."
"Very good reporting features."
"TeamCity is a very user-friendly tool."
"VCS Trigger: Provides excellent source control support."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"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."
"The integration is a valuable feature."
"Good integration with IDE and JetBrains products."
"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."
"Not user friendly for the layman."
"Its logging can be improved. When something goes wrong, it is not always very easy to find the problem. It is hard to identify whether the problem is because of low memory in the server or some configuration in Rational Build Forge. The error logs are not very detailed, and they should provide more information. It should also have more integration with third-party tools. It would be great to have more integration with third-party tools."
"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."
"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."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
Earn 20 points
IBM Rational Build Forge is ranked 19th in Build Automation while TeamCity is ranked 6th in Build Automation with 25 reviews. IBM Rational Build Forge is rated 9.0, while TeamCity is rated 8.2. The top reviewer of IBM Rational Build Forge writes "Great reporting features and very functional". On the other hand, the top reviewer of TeamCity writes "Build management system used to successfully create full request tests and run security scans". IBM Rational Build Forge is most compared with Jenkins, Bamboo and Digital.ai Release , whereas TeamCity is most compared with GitLab, CircleCI, Jenkins, Harness and GitHub Actions. See our IBM Rational Build Forge 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.