We performed a comparison between IBM Rational Build Forge and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."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."
"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."
"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."
"TeamCity is a very user-friendly tool."
"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."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"Not user friendly for the layman."
"If there was more documentation that was easier to locate, it would be helpful for users."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"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."
"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."
"I would suggest creating simple and advanced configurations. Advanced configurations will give more customizations like Jenkins does."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"The upgrade process could be smoother. Upgrading major versions can often cause some pain."
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 Tekton.
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.