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.
CloudBees Unify: Editions
CloudBeesExternal reviews
635 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Enterprise-Grade CI/CD Standardization with CloudBees
What do you like best about the product?
CloudBees’ greatest strength for large organizations lies in its capacity to standardize the software development and distribution (CI/CD) lifecycle. It goes beyond simply executing code by helping enforce best practices throughout the process. Leveraging Jenkins as its foundation, CloudBees offers centralized management, robust security, and scalable tools that turn disparate pipelines into a unified, reliable software factory for the whole enterprise.
What do you dislike about the product?
The main strengths of this tool are its orchestrated CI/CD engine and the implementation of quality gates. I rely on it to automate and manage the flow of code between different environments. With CloudBees CD, I set it up so that after code successfully passes unit tests, it is automatically put through security scans and compliance checks before being promoted to production. This process guarantees that only code which has been thoroughly verified and approved is deployed.
What problems is the product solving and how is that benefiting you?
CloudBees helped eliminate the clutter and inconsistencies that existed between our development teams. In the past, every team used its own version and configuration of Jenkins, which made auditing and migrating projects nearly impossible. With the platform now standardized, we've minimized variability and lowered the risk of failures in production. As a result, the speed at which we release new features has increased significantly, since the deployment process is now consistent and dependable for all teams.
Exceptional Enterprise Platform for Unified CI/CD
What do you like best about the product?
CloudBees stands out as an exceptional enterprise platform for software delivery, offering significant value to organizations like ours. While it is based on Jenkins, CloudBees enhances the experience by providing the security, scalability, and centralized management features that large companies require. These additions have enabled us to unify our CI/CD processes across many teams and hundreds of projects, achieving a level of process consistency that open-source Jenkins by itself cannot provide.
What do you dislike about the product?
CloudBees serves as an automated orchestration hub throughout the software lifecycle. I rely on it to achieve fast, secure, and consistent deployments. With CloudBees CI, I automate the building, testing, and integration of code immediately after any changes are committed. Following that, I use CloudBees CD to manage the promotion of code across our various environments—Development, QA, and Production—while applying quality and security gateways at every stage before the code is delivered to users.
What problems is the product solving and how is that benefiting you?
CloudBees has eliminated the confusion and risk that came with manual, fragmented deployments across different teams. In the past, every team managed its own Jenkins instance, which resulted in a disorganized mix of tools and increased vulnerabilities. With CloudBees, we now benefit from centralized, comprehensive visibility into the status of every code pipeline, from the initial commit all the way to production. This shift has significantly lowered our mean time to failure (MTTR), allowing us to deploy more frequently and with fewer mistakes.
Streamlines CI/CD and Enhances Team Efficiency
What do you like best about the product?
CloudBees helps in bringing everything in one place when it comes to managing software delivery. It helps in taking out the complexity of CI/CD pipelines and makes the entire process more organized and reliable. CloudBees provides the clear view of every step in the development and deployment process that helps in team work more efficiently and spot issues early before they cause the bigger issues.
What do you dislike about the product?
It is all over fine but one thing is that it's set process and configuration takes time.
What problems is the product solving and how is that benefiting you?
It has been very helpful for us to resolve the problems related to managing modern software delivery pipelines. It has resolved the biggest problem of lack of visibility and consistency in the development and deployment process. It has bring everything in one centralized platform that gives team a clear view of what's going on across builds, releases and tests that makes it much easier to track progress and find the issues early.
cloudbees jennkins cicd review
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.
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.
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.
It works, but its still just Jenkins at the end of the day
What do you like best about the product?
- Automated Upgrades
- Support available
- Plugin Compatibility
- Ability to operate multiple Jenkins in one UI
- 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
- 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
We dont have to worry about any maintenance from an ops perspective because of the easy to use automation at a grand scale
Cloudbees is a powerfull Release management tool
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)
Review 2024
What do you like best about the product?
Tool customization
Good and large Community
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
Streamlined deployment efficiency with excellent integration and comprehensive integration capabilities
What is our primary use case?
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.
Improves deployment speed with automation features
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.
Streamlined deployment and automation with enhanced efficiency
What is our primary use case?
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.
showing 1 - 10