Deployment and other processes are feasible for me, making this a smooth process. The integration part is good. We can use multiple things by integrating with CI/CD pipelines, and this is very feasible for us. This allows us to do our work easily. The productivity is very good. CloudBees is a good and efficient tool. We can work in client-facing scenarios, and since clients have provided these types of tools, we are able to work on them effectively.
CloudBees Unify: Editions
CloudBeesExternal reviews
631 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Comprehensive CI/CD with CloudBees, Needs GitOps Upgrade
What do you like best about the product?
I like CloudBees for its support and feature-rich version of Jenkins. The product helps automate the CI and CD process in a standard manner by requiring mandated steps in the pipeline, ensuring a formalized build and release process. I also find the unify platform promising for offering a single pane of glass view for multiple CI tools and its feature flagging capabilities.
What do you dislike about the product?
Jenkins is a bit outdated from a technology perspective and lacks the abilities to achieve a true GitOps model approach, something other competitive offerings like GitHub Actions provide. It needs modernizing to include more GitOps-based mechanisms and better integration with the PR process. It also could improve integration with the cloud for scaling execution planes, like using Azure ACA with KEDA.
What problems is the product solving and how is that benefiting you?
CloudBees automates our CI and CD processes in a standardized manner, ensuring a formalized build and release process.
Enterprise-Grade Reliability with Developer-Friendly Innovation
What do you like best about the product?
how it combines enterprise-grade reliability with developer-friendly innovation
What do you dislike about the product?
CloudBees builds on Jenkins and adds enterprise features, the platform can become quite complex.
What problems is the product solving and how is that benefiting you?
CloudBees primarily solves challenges around scaling, standardizing, and securing software delivery (CI/CD) in enterprise environments
Strong, Enterprise-Grade CI/CD for Centralized Jenkins Management
What do you like best about the product?
It is strong, enterprises grade CI/CD which is used for large scale organisation for jenkins environment with centralized management
What do you dislike about the product?
Dislike about Cloudbees is poor user experience like complicated setup or interface, difficult to configure and as it is depend on Jenkins which is outdated architecture which required manual power.
What problems is the product solving and how is that benefiting you?
It solves standardized CI/CD pipeline with centralised pipeline management along with pipeline templates which make easy for team to work.
Consistent automation has improved deployments and supports efficient client-facing workflows
What is most valuable?
What needs improvement?
For CloudBees, I can suggest that the log is very high, which is very hectic for us when trying to find which error is coming. This creates complexity. If possible, we could sort the logs so we can get the exact error on one page.
For how long have I used the solution?
I have been using ServiceNow for the last five plus years.
What do I think about the stability of the solution?
This is dependent on our JAR files and other code elements. If the code is large, it takes more time. If the code is less, it takes a short time. The deployment can take a couple of hours or a couple of minutes.
What other advice do I have?
We can upload the JAR file and deploy at the Jenkins level during our deployment. These types of labels and IDs can be deployed using CloudBees. Once we click to start the build, it automatically runs and automatically outputs the result, showing whether it succeeded or failed. If anything failed, we can check the logs in CloudBees, which is very interactive. I would rate this review 9 out of 10.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
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?
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.
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.
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.
showing 1 - 10