IBM Rational Build Forge vs Jenkins comparison

Cancel
You must select at least 2 products to compare!
IBM Logo
663 views|589 comparisons
100% willing to recommend
Jenkins Logo
6,756 views|5,825 comparisons
88% willing to recommend
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed IBM Rational Build Forge vs. Jenkins Report (Updated: May 2024).
771,212 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"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."

More IBM Rational Build Forge Pros →

"Jenkins optimizes the CI/CD process, enhances automation, and ensures efficiency and management of our build and deployment pipeline.""We used it for all continuous integration parts, like automation testing, deployment, etc.""GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins.""Configuration management: It is so easy to configure a Jenkins instance. Migrate configuration to a new environment just by copying XML files and setting up new nodes.""Jenkins has a lot of built-in packages and tools.""The initial setup is pretty simple.""We really appreciate that this solution is plug and play. When coding in the version control system, this product completes the build process automatically.""It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."

More Jenkins Pros →

Cons
"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."

More IBM Rational Build Forge Cons →

"I would like to have an integrated dashboard on top of it and a better UX to look at. The dashboard could be better in terms of integration with other tools. We should be able to have a single pane of glass across all the tools that we use where Jenkins is the pipeline. This can be a very good upgrade to it.""I think an integrated help button, that respected the context of the change/work in hand, would be a worthwhile improvement.""Jenkins is an open-source solution, and people tend to stay on the same version for a long time. When you look for an answer on Google, you often find something that doesn't relate to your implementation. The plugins are both the aspect of Jenkins and also one of the worst because the plugins can have different versions, so it's hard to figure out how to solve the problems.""There are some difficulties when we need to execute the DB script.""We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms.""The solution could improve by having more advanced integrations.""The support for the latest Java Runtime Environment should be improved.""Jenkins relies on the old version of interface for configuration management. This needs improvement."

More Jenkins Cons →

Pricing and Cost Advice
Information Not Available
  • "It is a free product."
  • "Jenkins is open source."
  • "​It is free.​"
  • "Some of the add-ons are too expensive."
  • "It's free software with a big community behind it, which is very good."
  • "I used the free OSS version all the time. It was enough for all my needs."
  • "Jenkins is open source and free."
  • "There is no cost. It is open source."
  • More Jenkins Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
    771,212 professionals have used our research since 2012.
    Comparison Review
    Anonymous User
    Moving to TeamCity from Jenkins At work, we’re slowly migrating from Jenkins to TeamCity in the hope of ending some of our recurring problems with continuous integration. My use of Jenkins prior to this job has been almost strictly on a personal basis, although I pretty much only use Travis nowadays. The biggest difference upon initial inspection is that TeamCity is far more focused on validating individual commits rather than certain types of tests. Jenkins’ front page presents information that is simply not useful in a non-linear development environment, where people are often working in vastly different directions. How many of the previous tests passed/failed is not really salient information in this kind of situation. Running specific tests for individual commits on TeamCity is far more trivial in terms of interface complexity than Jenkins. TeamCity just involves clicking the ”…” button in the corner on any test type (although I wish it wasn’t so easy to click “Run” by accident). I generally find TeamCity a lot more intuitive than Jenkins out of the box. There’s a point at which you feel that if you have to scour the documentation to do anything remotely complex in an application, you’re dealing with a bad interface. One disappointing thing in both is that inter-branch merges improperly trigger e-mails to unrelated committers. I suppose it is fairly difficult to determine who to notify about failure in situations like these, though. It seems like TeamCity pulls up the… Read more →
    Questions from the Community
    Ask a question

    Earn 20 points

    Top Answer:When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very easy… more »
    Top Answer:Jenkins has been instrumental in automating our build and deployment processes.
    Ranking
    19th
    out of 41 in Build Automation
    Views
    663
    Comparisons
    589
    Reviews
    0
    Average Words per Review
    0
    Rating
    N/A
    2nd
    out of 41 in Build Automation
    Views
    6,756
    Comparisons
    5,825
    Reviews
    37
    Average Words per Review
    382
    Rating
    7.9
    Comparisons
    Also Known As
    Rational Build Forge
    Learn More
    Overview

    IBM Rational Build Forge is an adaptive execution framework that helps automate and standardize the software assembly process. Rational Build Forge helps teams standardize repetitive tasks, improve software quality and manage compliance mandates. This software scales to 25 seats. Rational Build Forge delivers:
    Flexibility - gives developers self-service access to preconfigured build processes from within their integrated development environment (IDE). You can add IBM Rational software products to further enhance automation, reporting and integration.
    Productivity - accelerates build and release cycles through iterative development, parallel processes and efficient use of hardware.
    Compliance - simplifies compliance management with self-documenting audit trails and role-based security.
    Compatibility - increases team efficiency with centralized build and release management using the tools you have today.

    Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.

    Sample Customers
    Cars.com
    Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox
    Top Industries
    VISITORS READING REVIEWS
    Computer Software Company21%
    Financial Services Firm20%
    Educational Organization10%
    Insurance Company8%
    REVIEWERS
    Financial Services Firm33%
    Computer Software Company23%
    Media Company9%
    Comms Service Provider9%
    VISITORS READING REVIEWS
    Financial Services Firm21%
    Computer Software Company17%
    Manufacturing Company11%
    Government6%
    Company Size
    VISITORS READING REVIEWS
    Small Business21%
    Midsize Enterprise3%
    Large Enterprise76%
    REVIEWERS
    Small Business27%
    Midsize Enterprise16%
    Large Enterprise58%
    VISITORS READING REVIEWS
    Small Business17%
    Midsize Enterprise11%
    Large Enterprise72%
    Buyer's Guide
    IBM Rational Build Forge vs. Jenkins
    May 2024
    Find out what your peers are saying about IBM Rational Build Forge vs. Jenkins and other solutions. Updated: May 2024.
    771,212 professionals have used our research since 2012.

    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.