We performed a comparison between IBM Rational Build Forge and Jenkins 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."Very good reporting features."
"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."
"It has a lot of community posts and support."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"We can schedule anything with Jenkins, which is useful for deployment or anything that requires scheduling. It also has multiple plugins we can use for Maven, JUnit, etc."
"The deployment of traditional Jenkins is easy."
"There are a large number of plugins available for integration with third party systems."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"Having builds and test tasks triggered on commit helps not to break the product."
"Jenkins's open-based framework is very valuable."
"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."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"For this solution to be a 10, it has to be a lot more stable. Maybe the public version of Jenkins is stable, but in our case it's not stable."
"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."
"We need more licensed product integrations."
"Better and easy-to-use integration with Docker would be an improvement."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."
"And I don't care too much for the Jenkins user interface. It's not that user-friendly compared to other solutions available right now. It's not a great user experience. You can do just fine if you are a techie, but it would take a novice some time to learn it and get things done."
Earn 20 points
IBM Rational Build Forge is ranked 19th in Build Automation while Jenkins is ranked 2nd in Build Automation with 83 reviews. IBM Rational Build Forge is rated 9.0, while Jenkins is rated 8.0. The top reviewer of IBM Rational Build Forge writes "Great reporting features and very functional". On the other hand, the top reviewer of Jenkins writes "A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment". IBM Rational Build Forge is most compared with Bamboo and Digital.ai Release , whereas Jenkins is most compared with GitLab, Bamboo, AWS CodePipeline, Tekton and Harness. See our IBM Rational Build Forge vs. Jenkins 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.