External reviews
External reviews are not included in the AWS star rating for the product.
CloudBees Rollout
What do you like best about the product?
The ability to rollout or rollback specific features.
What do you dislike about the product?
Nothing, that I could see. It looked like a great step forward.
What problems is the product solving and how is that benefiting you?
We do not own the product but would use it for better feature release management.
- Leave a Comment |
- Mark review as helpful
Good product with ease of use, great support and Plugin collection
What do you like best about the product?
Ease of deployment of Jenkins , like other product available in marked cloudbee provide very easy to use platfrom
Variety of plugins and ease of use
great support and extra mile they go to help on problem
Variety of plugins and ease of use
great support and extra mile they go to help on problem
What do you dislike about the product?
Earlier their were issues with support but now they have greatly improved, UI can be more responsive
Migration tools to move to cloud bee
Migration tools to move to cloud bee
What problems is the product solving and how is that benefiting you?
CI CD pipeline, automation of the environment with benefits of seed jobs
Used by different teams
Used by different teams
Recommendations to others considering the product:
Go for it
System Director
What do you like best about the product?
Puedo ver el 100% de la trazabilidad de nuestros cambios
What do you dislike about the product?
Que la versión de Jenkins es más conocida que la versión empresarial
What problems is the product solving and how is that benefiting you?
Trazabilidad se los cambios y orquestamiento de los mismos
Recommendations to others considering the product:
Integración con kubernetes
I.T
What do you like best about the product?
work for different platform, configure in the OC and Master level
What do you dislike about the product?
agent have issue to communicate to master
What problems is the product solving and how is that benefiting you?
HA and JAVA issue
Rollout Review
What do you like best about the product?
Feature flags are very handy and allow entire features to be deployed or rolled back with little effort.
What do you dislike about the product?
I really didn't dislike anything. I think it's solid.
What problems is the product solving and how is that benefiting you?
Feature release management is the primary issue I am attempting to solve. So far, it's provided a very straightforward approach to resolving my issues.
Adapts to the needs of the area of operations in a simple way.
What do you like best about the product?
The centralized control that offers you over the masters, which you can deploy on new platforms such as kubernetes, user management and roles.
What do you dislike about the product?
The configuration on new platforms (kubernetes) is complicated.
What problems is the product solving and how is that benefiting you?
The way and speed of deploying changes to production is changing.
Seemless integration of slaves and clientmasters to one single operations center
What do you like best about the product?
Single sign on from Operations Center, Shared cloud and Shared agent features.
What do you dislike about the product?
Unable to configure multiple aws account when it comes to AWS plugins.
What problems is the product solving and how is that benefiting you?
Centralized way to manage multiple standalone jenkins. Collectively manage slave using Shared cloud / Shared agent feature. Everything can be managed from Operations center. We dont need to individually check each client masters to manage nodes.
Recommendations to others considering the product:
If an organization has single AWS account, then CloudBees core is good for them in all aspects. CloudBees modern platform is easy to setup and new modern UI is visually appealing. Easy to integrate with Gitlab and other tools. If an organization does not have LDAP, they can still use google SSO.
Simple, lightweight, effective
What do you like best about the product?
So far, my team and I have zero complaints about Rollout. The SDK was simple to install and it "just works" with minimal effort (speaking as a developer). In a few hours, I was able to set it up and start setting up A/B testing in our staging environment from specs provided by our product team. Can't ask for much more than that!
What do you dislike about the product?
To be honest, in a few months of using Rollout, I haven't run into any downsides to using it. There were no issues in the setup process, and the few minor questions I did have were answered promptly by the support team, even during the initial trial period.
What problems is the product solving and how is that benefiting you?
We're conducting A/B testing of new features and tweaks to existing features to improve our UX. So far, we've gathered measurable data which has helped in guiding my team in drafting new features based on the increased understanding of our user base.
Recommendations to others considering the product:
In my opinion, it's lightweight and as extendible as one desires. Its tagging system has given my team the flexibility it needs to implement everything we've been expected to build so far, and I can't currently think of a scenario in which it will be deficient in any way for our needs.
End to end software delivery
What do you like best about the product?
Compare to Jenkins it is more manageable and works better for the large scale operations teams. It has more security features and better flexibility. Also, it offers a better pricing model.
What do you dislike about the product?
Less variety of plugins especially when you need to deal with the enterprise systems.
What problems is the product solving and how is that benefiting you?
It would be a great option if you need to resolve elasticity and escaling issues while contributing to application orchestrations. Well integrated and manageable with Kubernetes.
Recommendations to others considering the product:
For enterprise-scale working with professional services at least in infrastructure, setup will help to avoid issues later on and works perfectly if you have everything influx.
Cloudbees saved my a$$ on my upgrade on our new server (my first upgrade killed the old server)
What do you like best about the product?
The cloudbees support representatives are well versed and knowledgable. They often will fill in the gaps that the Jenkins and plugin documentation have, especially when the person trying to work through it is not a Java programmer -- like me. It's been a challenge at times decifering where things go. But everytime I have had a question, I have been able to ask someone at Support, and received an answer quickly. I have learned alot about the Jenins system in the few months we have had Jenkins Support.
I love their attention to detail and step by step instructions. One of the first tickets I opened with them was to perform an upgrade to our current jenkins system. I received back a laundry list of things to check, steps to take, and the availability of a 30 minute phone call to review any questions or concerns I had with the process / procedure.
I love their attention to detail and step by step instructions. One of the first tickets I opened with them was to perform an upgrade to our current jenkins system. I received back a laundry list of things to check, steps to take, and the availability of a 30 minute phone call to review any questions or concerns I had with the process / procedure.
What do you dislike about the product?
Sometimes, the documentation can lack certain information, like where the file is that you need to update, or how to execute a specific script.
What problems is the product solving and how is that benefiting you?
I needed to add specific functionality to give my team the same capabilities we had on our original jenkins installation (that I trashed and only partially restored) after we merged our work with another department's Jenkin's installation.
CJS gave me the details on the plugin I needed to add, and then helped me plan out my upgrade with specific step by step instructions to ensure that I had a rollback plan in case there was an unexpected conflict or issue during the upgrade.
This was especially meaningful for me as our group had previously been using a very old version of Jenkins that I attempted to upgrade prior to obtaining a support contract with Cloudbees. The upgrade attempt crashed the server, and it took several days to get the server back up and running. At that point, I was still having issues with Jenkins and finally was able to get the program up and stable enough to provide only the most basic services.
As I learned more about jenkins, and what we could do I realized that we would need a more up to date solution. That was when I discovered that another department in ITS had a jenkins installation. I arranged for us to work with them, and we moved our projects over to be handled on that server. Unfortunately, in doing that, we lost an importatant piece of functionality that we had on our old decrepit jenkins server -- auto code deployment.
And thus began the work to upgrade the new Jenkins server, which I am thrilled to say went off without a hitch!
CJS gave me the details on the plugin I needed to add, and then helped me plan out my upgrade with specific step by step instructions to ensure that I had a rollback plan in case there was an unexpected conflict or issue during the upgrade.
This was especially meaningful for me as our group had previously been using a very old version of Jenkins that I attempted to upgrade prior to obtaining a support contract with Cloudbees. The upgrade attempt crashed the server, and it took several days to get the server back up and running. At that point, I was still having issues with Jenkins and finally was able to get the program up and stable enough to provide only the most basic services.
As I learned more about jenkins, and what we could do I realized that we would need a more up to date solution. That was when I discovered that another department in ITS had a jenkins installation. I arranged for us to work with them, and we moved our projects over to be handled on that server. Unfortunately, in doing that, we lost an importatant piece of functionality that we had on our old decrepit jenkins server -- auto code deployment.
And thus began the work to upgrade the new Jenkins server, which I am thrilled to say went off without a hitch!
Recommendations to others considering the product:
If you are running your own Jenkins server and using it for critical functions, it is well worth having a support contract. The money you spend today will save you misery tomorrow.
showing 421 - 430