CloudBees vs ServiceNow DevOps comparison

"It can manage multiple Jenkins instances."

"The customer support is good. You get good representatives from CloudBees to help you and understand your requirements."

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

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

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

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

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

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

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

"The platform could integrate better with other tools and support external tools directly."

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

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

"There are connection issues with CloudBees, specifically between Sybase and CloudBees. W"

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

"To improve efficiency, they should focus on smoother label deployment."

"It could improve the document upload process."

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

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

"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 is our biggest concern with the solution."

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

"Though it is an expensive solution, it is an affordable one, in my opinion."

"It's very expensive, so some organizations can't afford the additional license."

"We consider the pricing to be inordinately expensive and may deter others from choosing the solution"