CloudBees vs Jenkins comparison

CloudBees and Jenkins are both solutions in the Build Automation category. CloudBees is ranked #7 with an average rating of 8.3, while Jenkins is ranked #3 with an average rating of 8.1. CloudBees holds a 1.1% mindshare in BA, compared to Jenkins’s 10.4% mindshare. Additionally, 100% of CloudBees users are willing to recommend the solution, compared to 87% of Jenkins users who would recommend it.

CloudBees

Read 20 CloudBees reviews

770 Views
148 Comparison Views

100% willing to recommend

Jenkins

Read 93 Jenkins reviews

4,156 Views
3,557 Comparison Views

87% willing to recommend

CloudBees

Jenkins

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Mar 5, 2025

Jenkins and CloudBees compete in the continuous integration space. Based on the comparison, CloudBees seems to have an advantage in terms of scalability and enterprise-level features, while Jenkins excels in flexibility and community support.

Features: Jenkins is known for its vast library of plugins, enabling seamless integration with a wide range of third-party systems. This makes it a versatile option for varied automation needs. CloudBees offers advanced security features and supports managing multiple Jenkins instances, enhancing its appeal to large teams handling complex projects. Both tools support customizable pipelines and integration with major tools, but CloudBees stands out with its enterprise-focused capabilities.

Room for Improvement: Jenkins could improve by enhancing the stability of lesser-used plugins and simplifying installation. Additionally, its interface would benefit from modernization, and increased documentation on plugin development could enhance user experience. CloudBees could address performance issues encountered during large-scale operations and improve the intuitiveness of its user interface. Reducing update dependencies on vendor priorities could also be beneficial.

Ease of Deployment and Customer Service: Jenkins offers deployment flexibility across various environments like on-premises and public clouds. It relies on community support, providing vast resources but sometimes lacks immediacy. CloudBees, with its enterprise-grade deployment capabilities, offers structured customer support, quicker resolution times, and tailored assistance as part of its premium service, albeit with potential cost implications.

Pricing and ROI: Jenkins, being open-source, involves no licensing fees, making it a cost-effective choice that provides good ROI by enhancing productivity through automation. CloudBees, while more expensive, offers significant value due to its advanced features and enterprise-readiness. Organizations with complex continuous integration needs may find CloudBees worth its price for its comprehensive support and capabilities.

To learn more, read our detailed CloudBees vs. Jenkins Report (Updated: April 2025).

Buyer's Guide

CloudBees vs. Jenkins

April 2025

Download the complete report

Helped 849,190 peers since 2012

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Categories and Ranking

CloudBees

Ranking in Build Automation

7th

Average Rating

8.4

Reviews Sentiment

7.4

Number of Reviews

Ranking in other categories

Configuration Management (11th), Value Stream Management Software (3rd), DevSecOps (5th)

Jenkins

Ranking in Build Automation

3rd

Average Rating

8.0

Reviews Sentiment

7.0

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of CloudBees is 1.1%, up from 0.1% compared to the previous year. The mindshare of Jenkins is 10.4%, down from 13.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Build Automation

Featured Reviews

YashBrahmani

Senior Associate at BNP Paribas CIB

Offers a clear visualization and overview of workflows and helpful in managing CI/CD processes

Improvement in the sense that they can do better in terms of management of logs and stuff like that because the console logs are very extensive, and that causes a lot of storage issues. That is one of the things which is there. Also, with respect to the traditional platform and the modern platform, many things have upgraded, and it has quite improved. But when we talk about the performance of the agents, it’s still very crucial because it’s not up to par. It takes a lot of time to provision the agent and to finish the build because of the SSH connection and the JNLP connection. Due to that, sometimes the agent doesn’t get provisioned. Those are some of the blockers that meet up the time in terms of administering the instance.

Read full review

Dinesh-Patil

Consultant at a manufacturing company with 10,001+ employees

A highly-scalable and stable solution that reduces deployment time and produces a significant return on investment

The dashboard needs to be improved. Though the access management and authentication functionalities are present, the dashboard and UI could be more user-friendly. The product has many plug-ins. Users have to go through the documentation to be able to use the product. The UI must be more user-friendly. The information should be available in the dashboard itself. The users shouldn’t have to refer to the documentation. When a user hovers over the elements on the dashboard, it should reveal information about them.

Read full review

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros

"It’s a very good tool for auditing your project pipelines as well."

"The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar, management master to CloudBees, Blue Ocean, JobConfig, and support."

"CloudBees assists by automating tasks, previously done manually, in the pipeline setup."

"The solution's most valuable feature is its flexibility."

"CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization."

"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."

"CloudBees's user interface is very simple and user-friendly."

"CloudBees is a user-friendly tool."

More CloudBees pros

"The automated elements are easy to use and you can put them into your server."

"Jenkins has excellent task planning features."

"We have started to integrate Pipelines as a part of a build, and built a library of common functions. It simplified and made our build scripts more readable."

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

"It's a powerful tool for CI/CD."

"This is a great integration tool and very powerful."

"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

"Jenkins has a lot of built-in packages and tools."

More Jenkins pros

Cons

"One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time."

"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."

"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."

"We did face some challenges, particularly with the infrastructure."

"I think a preview of the errors would be good just at the point where the error occurs."

"There could be improvements in the ease of use."

"I would like to see improved speed and availability."

"We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly."

More CloudBees cons

"The upgrades need improvement."

"We need more licensed product integrations."

"The bug fix speed is very slow."

"The documentation could be more friendly, and more examples of how to use it."

"Centralized user management would be helpful."

"Jenkins could improve in areas related to Kubernetes and Docker container integration, like machine allocation of nodes and Marshaling integration improvements."

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

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

More Jenkins cons

Pricing and Cost Advice

Information not available

"I used the free OSS version all the time. It was enough for all my needs."

"The solution is open source."

"Jenkins is open source."

"It is an open source."

"Jenkins is open-source, so it is free."

"The solution is one of the lowest costs compared to competitors."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"Jenkins is an open-source tool."

More Jenkins pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Build Automation solutions are best for your needs.

See recommendations

849,190 professionals have used our research since 2012.

Comparison Review

it_user184734

Systems Administrator at Facebook

Jan 22, 2015

I generally find TeamCity a lot more intuitive than Jenkins.

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…

Read full review

Top Industries

By visitors reading reviews

Financial Services Firm

27%

Legal Firm

11%

Manufacturing Company

11%

Computer Software Company

Financial Services Firm

22%

Computer Software Company

17%

Manufacturing Company

11%

Government

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

Questions from the Community

What needs improvement with CloudBees?

There are connection issues with CloudBees, specifically between Sybase and CloudBees. We often encounter connection problems, and there are issues with the pipelines.

See all answers

What is your primary use case for CloudBees?

We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.

See all answers

What advice do you have for others considering CloudBees?

I would recommend CloudBees to others because building jobs is much easier than with other solutions.

See all answers

How does Tekton compare with Jenkins?

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 e...

See all answers

What do you like most about Jenkins?

Jenkins has been instrumental in automating our build and deployment processes.

See all answers

What is your experience regarding pricing and costs for Jenkins?

Jenkins is used in many companies to save money, especially within R&D divisions, by avoiding the expenses of proprietary tools.

See all answers

Comparisons

GitLab vs CloudBees

Compared 53% of the time

Harness vs CloudBees

Compared 29% of the time

Tekton vs CloudBees

Compared 18% of the time

More CloudBees Competitors

GitLab vs Jenkins

Compared 15% of the time

Harness vs Jenkins

Compared 14% of the time

Bazel vs Jenkins

Compared 9% of the time

Bamboo vs Jenkins

Compared 9% of the time

Tekton vs Jenkins

Compared 8% of the time

More Jenkins Competitors

Product Reports

Buyer's Guide

CloudBees

April 2025

Download CloudBees product report

Buyer's Guide

Jenkins

April 2025

Download Jenkins product report

Overview

CloudBees DevOptics is a robust software utilized primarily to enhance CI/CD processes by offering real-time visibility into Jenkins pipelines. It facilitates effective monitoring, incident management, and decision-making through comprehensive data analysis. Users value its features like DevOps performance metrics and seamless tool integration, leading to improved operational efficiency and productivity in organizations.

CloudBees

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

Jenkins

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee

Airial, Clarus Financial Technology, cubetutor, Metawidget, mysocio, namma, silverpeas, Sokkva, So Rave, tagzbox

Buyer's Guide

CloudBees vs. Jenkins

April 2025

Free Report: CloudBees vs. Jenkins

Find out what your peers are saying about CloudBees vs. Jenkins and other solutions. Updated: April 2025.

DOWNLOAD NOW

849,190 professionals have used our research since 2012.

See our CloudBees 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.