Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Reviews from AWS customer

2 AWS reviews
  • 5 star
    0
  • 2
  • 3 star
    0
  • 2 star
    0
  • 1 star
    0

External reviews

630 reviews
from and

External reviews are not included in the AWS star rating for the product.


    Shaik S.

cloudbees jennkins cicd review

  • July 27, 2025
  • Review provided by G2

What do you like best about the product?
cloudbees jenkins we have lot of uses.
1.we can create n number of controllers in same operation center.
2. Easy to intergration with other tools like sonar,jira,maven,gradel,ant....
3.we have good customer support when we have issues anything with installation and access and infra.
4.We have easy of implementing with casc bundles and controllers.
5.we will use same operation center to create stage,prod,dev controllers so here easy of use.
6.cloudbees jenkins having good level security and frequency of use product awesome.
What do you dislike about the product?
I don't have any thing but improve extra features.
What problems is the product solving and how is that benefiting you?
Solving easy of tracking’s application in stage ,dev,prod
becasue we are going to use three controllers for three envs.
easy of implementing new integration tools with cloudbees jenkins.
using different agents using in pipeline script.


    Accounting

It works, but its still just Jenkins at the end of the day

  • February 13, 2025
  • Review provided by G2

What do you like best about the product?
- Automated Upgrades
- Support available
- Plugin Compatibility
- Ability to operate multiple Jenkins in one UI
What do you dislike about the product?
- It's still just Jenkins at the end of the day
- Price Tag
What problems is the product solving and how is that benefiting you?
It takes care of our CI from commit to release really effectively
We dont have to worry about any maintenance from an ops perspective because of the easy to use automation at a grand scale


    Adrien C.

Cloudbees is a powerfull Release management tool

  • November 15, 2024
  • Review provided by G2

What do you like best about the product?
Cloudbees is very useful for following our application deployements, the workflows used could have a lot of complex features
What do you dislike about the product?
The graphical user interface could be improve, lot of widgets are not standard, and search is case sensitive could be a real pain.
What problems is the product solving and how is that benefiting you?
Release orchestration with a lot of integration with our others tools (jira, gitlab, awx, sonarqube)


    Miquel Angel G.

Review 2024

  • November 13, 2024
  • Review provided by G2

What do you like best about the product?
Tool customization
Good and large Community
What do you dislike about the product?
Poor documentation in some topics for example with CasC
What problems is the product solving and how is that benefiting you?
CICD Global orchestration in all my technologies


    Lokesh Katamaneni

Streamlined deployment efficiency with excellent integration and comprehensive integration capabilities

  • October 09, 2024
  • Review provided by PeerSpot

What is our primary use case?

The primary use case for CloudBees is for continuous integration and deployment. It is primarily used for production deployments. We use it to trigger Autobahn, such as CloudBees, well in advance to clear out many issues upfront, trigger change requests, and test in various environments to be ready with the production deployment on the actual date.

How has it helped my organization?

CloudBees has helped our organization by integrating with various systems like version one, GitHub, and PDSM. It reduces the need for documentation by automating processes, saving time when creating documents and testing the application. This reduces the amount of time spent on deployments and helps pull out all the test results and create change requests, providing a more streamlined process for deployment.

What is most valuable?

The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDSM. It automates documentation and testing processes, reducing the need to create documents manually. By creating automated processes, it saves time and effort.

What needs improvement?

It could improve the document upload process. Currently, documents need to be uploaded manually to the PDSM request. An enhancement could be to have a feature where you can upload documents directly to go into the PDSM request.

For how long have I used the solution?

For about two to three years, approximately two and a half to three years.

What do I think about the stability of the solution?

CloudBees has improved a lot over time. Initially, there were challenges setting it up, but once we understood its functions and processes, there were no stability issues.

What do I think about the scalability of the solution?

CloudBees is scalable as it integrates with various complex systems and offers the flexibility to scale to many other application integrations beyond those currently used.

How are customer service and support?

I have not personally interacted with customer service or support since the DevOps team handles template creation and maintenance, and they might have contacted support during the initial phase.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before CloudBees, we did not use a similar tool. However, we are currently considering a transition to GitHub Actions.

How was the initial setup?

The initial setup involved creating a template that checks pull requests in GitHub. It verifies approvals, mergers, and other criteria necessary for a build. The setup includes extensive integration with other systems, stringent checks, and a series of deployment stages from QA to production.

What about the implementation team?

The DevOps team is responsible for creating templates and handling integration with various systems. They play a crucial role in supporting the implementation and deployment processes.

What was our ROI?

The measurable benefits of using CloudBees include a significant amount of time saved during deployment because of the automation and integration capabilities it offers.

What's my experience with pricing, setup cost, and licensing?

I am not aware of the pricing, setup cost, or licensing details for CloudBees.

Which other solutions did I evaluate?

We are currently using GitHub Actions, with an effort to transition from CloudBees to GitHub Actions.

What other advice do I have?

Follow the guidelines and step-by-step processes thoroughly. If you encounter integration issues with your tools, seek support from CloudBees to ensure integration. Once set up, CloudBees is a reliable tool for deployment.

I'd rate the solution nine out of ten.


    Vaddi Yashoda Lakshmi

Improves deployment speed with automation features

  • October 07, 2024
  • Review provided by PeerSpot

What is our primary use case?

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

How has it helped my organization?

CloudBees has made deployment faster compared to on-premise solutions. It also facilitates working with multiple machines, improving efficiency and performance.

What is most valuable?

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.

What needs improvement?

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

For how long have I used the solution?

I have been working with CloudBees for one and a half years.

What do I think about the stability of the solution?

There are a lot of connection issues with CloudBees. We experience disconnections frequently.

What do I think about the scalability of the solution?

CloudBees supports the deployment of large amounts of data efficiently across multiple machines.

How are customer service and support?

I haven't gone through the technical support, so I can't comment on it.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before CloudBees, we were using Jenkins on-premises. We switched to CloudBees because we moved our SQL servers to the cloud, which made deployment easier.

How was the initial setup?

The initial setup of CloudBees took approximately fifteen to twenty minutes.

What about the implementation team?

We used UrbanCode deployment to deploy it in different environments, but I was not directly involved in the implementation part.

What was our ROI?

I am not aware of the return on investment metrics for CloudBees.

What's my experience with pricing, setup cost, and licensing?

I am not sure about the pricing, setup cost, and licensing for CloudBees. The team takes care of it.

Which other solutions did I evaluate?

I am not aware of any other solutions that were evaluated before choosing CloudBees.

What other advice do I have?

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other


    Sinthusan Thangarajah

Streamlined deployment and automation with enhanced efficiency

  • October 03, 2024
  • Review provided by PeerSpot

What is our primary use case?

We use a pipeline to deploy our application. All our organization checks and requirements are added to the CloudBees pipelines, ensuring code quality and checking vulnerabilities. We use Jenkins and SonarQube as part of the deployment process.

How has it helped my organization?

CloudBees has streamlined our deployment process. Previously, deployment involved manual file transfers and checks, which were time-consuming. Now, with CloudBees, many tasks are automated, making our work easier and more efficient.

What is most valuable?

CloudBees assists by automating tasks, previously done manually, in the pipeline setup. This saves time and improves efficiency. The features set rules that are regularly updated, reducing the need for constant oversight. One-click deployment processes also highlight the flexibility and ease of the platform.

What needs improvement?

Sometimes, there are performance issues, however, they may be due to our organization's configuration. Currently, I do not have specific improvements in mind as these might be related to our side.

For how long have I used the solution?

Previously, our organization had an on-premise solution, but we have moved to the cloud version.

What do I think about the stability of the solution?

Due to security constraints within our organization, the performance can appear slow. It is difficult to discern if the issue is with CloudBees or our organization's configuration.

What do I think about the scalability of the solution?

CloudBees is scalable, but I cannot provide specific details on how this scalability impacts us.

How are customer service and support?

We experience issues with the CloudBees pipelines occasionally, like resource limits or permission errors. The DevOps team generally resolves these, and I would rate CloudBees support eight out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before CloudBees, we used FTP for deployment, which involved no pipelines.

How was the initial setup?

The setup was managed by a separate team. My experience starts with using the product, which was straightforward.

What about the implementation team?

A separate team, the DevOps team, manages the CloudBees setup and any technical support needed.

What was our ROI?

CloudBees saves time and resources by executing automated deployment processes, which would otherwise have been manual and time-consuming.

What's my experience with pricing, setup cost, and licensing?

I am not aware of the pricing, setup cost, or licensing details.

Which other solutions did I evaluate?

I have not evaluated other solutions, as my interaction began with CloudBees directly.

What other advice do I have?

I would recommend CloudBees, especially to those using traditional ways of deployment, because it simplifies and automates many processes.

Which deployment model are you using for this solution?

Public Cloud


    Jonatas L. R. Costa

Efficient feature deployment with robust DevOps capabilities

  • September 16, 2024
  • Review provided by PeerSpot

What is our primary use case?

We use CloudBees Jenkins with Jenkins and Sonar validation for our pipeline. We use it for all microservices, web system payment integrations, and overall pipeline configurations and deployment processes.

How has it helped my organization?

CloudBees has improved our DevOps practices by allowing us to deploy features and fixes efficiently. It supports our business rules, security analysis, and overall deployment process while simplifying the configuration.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been working with CloudBees for around two to three years.

What do I think about the stability of the solution?

CloudBees is very stable and reliable. From one to ten, I would rate the stability a ten.

What do I think about the scalability of the solution?

CloudBees offers high scalability. On a scale from one to ten, I would rate its scalability a ten.

How are customer service and support?

Customer service and technical support are excellent. I rate the technical support from one to ten as a ten. They provide fast, simple, and efficient support.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before using CloudBees, we used Jenkins SonarQube, Nexus, Azure, and AWS. The decision to switch to CloudBees was made for better integration and deployment capabilities.

How was the initial setup?

The initial setup of CloudBees is very easy and straightforward. It takes around 20-30 minutes to deploy completely without any complicated steps.

What about the implementation team?

Our configuration team handled the setup and deployment. Twenty people were involved in the deployment and maintenance processes, and they ensured everything worked perfectly without delays.

What other advice do I have?

CloudBees provides a robust and efficient solution for our DevOps needs. Ensuring an intuitive user interface and simplifying the setup process can further enhance its usability for new users.

Which deployment model are you using for this solution?

Public Cloud


    Suryansh Srivastava

A single person can still control all the masters

  • September 09, 2024
  • Review provided by PeerSpot

What is most valuable?

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.

It has dynamic node allocation for the code we're building. When we trigger a build, like for Java code, it pulls a Docker image from a repository. Then, a pod spins up. If you have ten nodes, the solution uses a Kubernetes architecture. There's one master node and ten different nodes connected to the master. Whenever we trigger a build, a pod spins up and gets scheduled on any of the slave nodes in the Kubernetes cluster. That's the best thing I see about the product. 

The management is good. You don't need to manage different nodes individually. You don't have to specify which node to build the code on. In CloudBees, you can avoid that. You mention the node, and it will automatically schedule the pod on whichever node is free.

You can also configure different nodes. Another good point is that you can configure Elastic File System to store the data.

What needs improvement?

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.

For how long have I used the solution?

I have been working with the product for three years. 

What do I think about the stability of the solution?

I have no issues with the tool's stability. 

What do I think about the scalability of the solution?

I find the product scalable. Currently, we're using a Kubernetes architecture and working on-premises. However, other teams are working on the cloud version of CloudBees with AWS infrastructure. There, we can also scale the nodes.

I'm currently working for an organization that has over 200 applications. They've adopted the CloudBees architecture. So, these 200 applications have 200 different masters. All of this is managed by a single team, which is a separate team. The different applications and different members are managed by a single person who oversees the entire organization, similar to how we have it in AWS.

How are customer service and support?

The tool's support is good. 

How would you rate customer service and support?

Neutral

What other advice do I have?

I don't think CloudBees requires much maintenance, but some things must be considered. As I said, they have a Kubernetes architecture, so Kubernetes patching and Jenkins patching will also be required. It publishes upgraded versions on its website. You can purchase the latest license and upgrade the Jenkins version through that purchase.

I rate the overall solution an eight out of ten. 

Which deployment model are you using for this solution?

On-premises


    Aaron Sarkar

User-friendly, but the pipelines randomly fail multiple times

  • September 03, 2024
  • Review provided by PeerSpot

What is most valuable?

CloudBees is a user-friendly tool.

What needs improvement?

I think the pipeline design we had on CloudBees was not very intuitive. There were a couple of reasons for this. The first reason was the way we went about merging our code. When we have code, we would just put it on GitLab. Realistically, GitLab already provides CI/CD pipelines. We shouldn't be using CloudBees because it's a third-party source we don't need.

We started realizing that CloudBees was not the right tool for that. The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times. The failures wouldn't be related to a test that we would have.

It became such a huge problem that pipeline issues became a whole other domain that we would end up exploring through different developers. Because of that, we're actually moving away from CloudBees now and looking into just making GitLab pipelines.

What do I think about the stability of the solution?

I rate the solution’s stability a five out of ten.

What do I think about the scalability of the solution?

We scaled the solution, and it's a major part of the company. Since tons and tons of products are using CloudBees, I don't think it has a problem with scalability.

How was the initial setup?

I've worked a bit with the deployment of the pipeline. I don't want to say I made my own pipeline, but I merged two repositories and made my own pipeline out of them. It took me almost a week's worth of work and a lot of random failures here and there.

The setup will not be too complicated if you have good knowledge of it. It wasn't that easy for me because I was still like an intern who had just started.

What other advice do I have?

I wouldn't say anybody can use the solution. CloudBees is a user-friendly tool, but it's a bit confusing to navigate in certain places. It wasn't confusing, but it was a bit unintuitive. On the other hand, the GitLab pipelines we started migrating towards were significantly more user-friendly.

The solution's integration with other tools is fine, and I rate it a six out of ten. We integrated with GitLab, and it was fine. We did have a lot of problems, though, and we would have people working until past midnight trying to fix those. It was kind of a problem on that end. It was getting the job done eventually, but it had many ghost problems.

People would end up waiting for weeks to merge perfectly good code just to make it work for this pipeline that was having problems. It was very annoying from that standpoint.

I don't think there's any actual problem with CloudBees. Our problems with CloudBees could have been specific to our code, development practices, and how we used the tool. At the end of the day, it's not about the tool itself, but it's about how you use the tool. There may be a problem with the way we were using the tool. I think CloudBees is still good.

At the end of the day, it did get the job done for a lot of things. I have to give it credit where it's due. I would recommend CloudBees to other users. In my opinion, having a third-party pipeline when your repository already provides a pipeline doesn't make any sense to me. If GitLab is providing a pipeline, use that pipeline, which is more intuitive. It's also fine if you want to use CloudBees as a secondary pipeline support.

Overall, I rate the solution six and a half out of ten.