CloudBees vs Jenkins comparison

CloudBees and Jenkins are both solutions in the Build Automation category. CloudBees is ranked #6 with an average rating of 8.3, while Jenkins is ranked #3 with an average rating of 8.1. CloudBees holds a 1.4% mindshare in BA, compared to Jenkins’s 10.5% 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

977 Views
791 Comparison Views

100% willing to recommend

Jenkins

Read 93 Jenkins reviews

3,699 Views
3,625 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: July 2025).

Buyer's Guide

CloudBees vs. Jenkins

July 2025

Download the complete report

Helped 860,745 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

6th

Average Rating

8.4

Reviews Sentiment

7.4

Number of Reviews

Ranking in other categories

Configuration Management (11th), Value Stream Management Software (2nd), DevSecOps (4th)

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 July 2025, in the Build Automation category, the mindshare of CloudBees is 1.4%, up from 0.2% compared to the previous year. The mindshare of Jenkins is 10.5%, down from 12.7% 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

Mahdi Mallaki

Senior Devops Engineer at Rakuten

Has a community of plugin providers but needs improvement in Kubernetes integration

Integrating Jenkins with other tools or solutions has presented some challenges. For instance, when attempting to integrate Jenkins with Kubernetes, I encountered numerous errors, which took several days to resolve. In Jenkins, adding a feature typically involves incorporating the repository feature separately. Jenkins lacks built-in Git repository functionality, necessitating an external Git repository to store Jenkins manifests. In contrast, GitLab offers an integrated Git repository and pipeline runner, streamlining the process. One improvement for Jenkins could be integrating a Git server, simplifying the management of CI/CD pipelines. Currently, with Jenkins, modifying pipeline manifests requires navigating to a separate Git repository. In GitLab, however, manifest changes can be made directly within the repository.

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

"The most valuable feature of the solution is that its GUI is quite simple."

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

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

"Scalability largely depends on how the tool is set up within your infrastructure"

"CloudBees updates its features frequently, so if we need something like SSL login, they enable it."

"I find the automation feature most valuable. CloudBees is highly scalable and supports both small and large teams. The deployment process is also faster when compared to on-premise."

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

"One recent product feature that stands out is the pipeline explorer, which is providing significant value for us right now."

More CloudBees pros

"The simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."

"It has a lot of community posts and support."

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

"The most valuable aspect of this solution is that there are multiple features. We can abstract certain variables and then build our deployment routine while being able to do some abstraction onto the SSH connections."

"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."

"It's very easy to learn."

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

"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."

More Jenkins pros

Cons

"The user interface of CloudBees is good but could be even more intuitive. Improving the user-friendliness of the interface and having simpler setup configurations would greatly benefit new users."

"A lot of stability issues are there with CloudBees."

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

"Sometimes, there are performance issues, however, they may be due to our organization's configuration."

"It could improve the document upload process."

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

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

"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."

More CloudBees cons

"The documentation on plugin development could be better: more examples. "

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

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

"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."

"There is no way for the cloud repositories to trigger Jenkins."

"The support for the latest Java Runtime Environment should be improved."

"They need to improve their documentation."

More Jenkins cons

Pricing and Cost Advice

Information not available

"It is free."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"Jenkins is not expensive and reasonably priced."

"Jenkins is an open-source platform."

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

"The tool is open-source."

"There is no cost. It is open source."

"In our company, we do pay for the licensing of the solution."

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

860,745 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

25%

Manufacturing Company

12%

Legal Firm

11%

Computer Software Company

Financial Services Firm

22%

Computer Software Company

16%

Manufacturing Company

12%

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 50% of the time

Harness vs CloudBees

Compared 26% of the time

Digital.ai Release vs CloudBees

Compared 12% of the time

Tekton vs CloudBees

Compared 12% of the time

More CloudBees Competitors

Harness vs Jenkins

Compared 17% of the time

GitLab vs Jenkins

Compared 14% of the time

Bazel vs Jenkins

Compared 9% of the time

Tekton vs Jenkins

Compared 8% of the time

Bamboo vs Jenkins

Compared 7% of the time

More Jenkins Competitors

Product Reports

Buyer's Guide

CloudBees

July 2025

Download CloudBees product report

Buyer's Guide

Jenkins

June 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

July 2025

Free Report: CloudBees vs. Jenkins

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

DOWNLOAD NOW

860,745 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.