Try our new research platform with insights from 80,000+ expert users

CloudBees vs ServiceNow DevOps comparison

 

Comparison Buyer's Guide

Executive Summary

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 Value Stream Management Software
3rd
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
20
Ranking in other categories
Build Automation (7th), Configuration Management (12th), DevSecOps (5th)
ServiceNow DevOps
Ranking in Value Stream Management Software
4th
Average Rating
7.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Value Stream Management Software category, the mindshare of CloudBees is 0.4%, down from 0.4% compared to the previous year. The mindshare of ServiceNow DevOps is 3.4%, down from 5.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Value Stream Management Software
 

Featured Reviews

YashBrahmani - PeerSpot reviewer
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.
Dinesh Khanna - PeerSpot reviewer
A tool that offers useful templates and is very easy to integrate with CI/CD tools
Initially, I faced some difficulties with the product's initial setup phase. After handling the setup phase for other applications, I don't feel the need to take much time to handle the integration or implementation part attached to the solution. The solution is deployed on the public cloud services offered by Azure. The time needed to take care of the deployment phase of the solution depends on the project and the weightage of an application in an environment. It is important to see how long it takes to handle the deployment process stage by stage. During the product's testing part, it takes time since there is a need to take care of the integration part along with unit testing, functional testing, and performance testing before it is made available specifically for an environment after considering aspects from a security point of view. After the aforementioned aspects are taken care of, the product needs to go for business approvals and then through stages, including the QA stage, before reaching the final stage related to production and deployment. Our organization has more than 20 applications that we manage with the help of the solution, because of which most of the things are automated across the company, and only three or four people are sufficient to handle all the applications.

Quotes from Members

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

Pros

"Scalability largely depends on how the tool is set up within your infrastructure"
"It can manage multiple Jenkins instances."
"CloudBees is a user-friendly tool."
"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."
"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."
"The initial setup is easy."
"CloudBees's user interface is very simple and user-friendly."
"The API part of the solution is very easy to integrate with CI/CD tools, which helps our company achieve our goals related to the integration part."
"I have found the ease of CACD integration to be the most valuable feature."
"It's very user-friendly. It has a reporting side that is very automated. There are a lot of things that you can automate using that tool."
"We use it for a lot of things, and it is really good for our use cases. We use it for our help desk and knowledge management, which is really good. When it comes to modules, it has an incident module, which is really good for us in terms of tracking our cases and incidents. Its change management module is really good, and it also has customization capabilities."
 

Cons

"I think a preview of the errors would be good just at the point where the error occurs."
"A lot of stability issues are there with CloudBees."
"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."
"I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines."
"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."
"There are connection issues with CloudBees, specifically between Sybase and CloudBees. W"
"It could improve the document upload process."
"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."
"Pricing is our biggest concern with the solution."
"Its performance is really bad. When you're on the hosted cloud, it gives you the time it takes for a transaction to happen, and it takes anything from 20 seconds to a minute, which is a really long time. Something that is really annoying in this solution is that when you click on the Back button to go back, you don't go back to the previous screen. You go back all the way to the homepage. It is really annoying and painful. Its UI is also pretty dated. It is very customizable, but the customization seems to be clunky. We have a separate team that owns the ServiceNow implementation. They control how it is customized. Its customizations are pretty extensive, and it takes us a while to get them done, which is painful. That could be because of our internal team, as opposed to the product itself. When it comes to DevOps, there are better solutions such as Atlassian and Azure DevOps. ServiceNow DevOps is an ITIL product that is trying to be something else. DevOps is not its prime purpose, even though it is capable of doing that. Trying to be too many things by one platform is not a good idea. They should focus on the ITIL space and not get into all other spaces."
"The roles for the ServiceNow administration side could be improved. I think they could be more specific or add the descriptions for the different roles."
"From a documentation point of view, there are certain areas of concern, and improvements are to be made to make the documentation part clearer and crisper."
 

Pricing and Cost Advice

Information not available
"We consider the pricing to be inordinately expensive and may deter others from choosing the solution"
"It's very expensive, so some organizations can't afford the additional license."
"Though it is an expensive solution, it is an affordable one, in my opinion."
report
Use our free recommendation engine to learn which Value Stream Management Software solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Manufacturing Company
14%
Legal Firm
12%
Non Profit
7%
Financial Services Firm
36%
Manufacturing Company
17%
Healthcare Company
9%
Insurance Company
6%
 

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.
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.
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.
What do you like most about ServiceNow DevOps?
The API part of the solution is very easy to integrate with CI/CD tools, which helps our company achieve our goals related to the integration part.
What needs improvement with ServiceNow DevOps?
As of now, our company doesn't see any area where the solution has any shortcomings. From a documentation point of view, there are certain areas of concern, and improvements are to be made to make ...
What is your primary use case for ServiceNow DevOps?
My company is in the process of integrating Azure DevOps with ServiceNow. The solution is mainly used for deployment purposes with change requests whenever there is a need to do production, deploym...
 

Comparisons

 

Overview

 

Sample Customers

Capital One, PEGA, vistaprint, HSBC, BOSCH, Starbucks Coffee
Syntax, Bridgewater Bank, Capita
Find out what your peers are saying about CloudBees vs. ServiceNow DevOps and other solutions. Updated: January 2025.
832,138 professionals have used our research since 2012.