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."
"A lot of support material exists via a single web search of exactly what you're looking for."
"The deployment of traditional Jenkins is easy."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"Has a good interface, is reliable and saves time."
"The most valuable feature is its ability to connect with different tools and technologies."
"Distributed execution of build and test jobs."
"Jenkins is the most widely used development tool, so there are many plugins and it's easy to integrate. There is a large user base to provide community support, which I find very valuable. If I need to find a better way to do something, I can always get help from the community. Automation is about thinking outside of the box, and other users are constantly adding new plugins."
"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."
"The solution could improve by having more advanced integrations."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"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."
"A more user-friendly UI for creating pipelines would be helpful."
"Jenkins could simplify the user interface a little bit because it sometimes creates too many features cramped in the UI."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"The learning curve is quite steep at the moment."
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, Harness and Tekton. 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.
