CloudBees Unify: Editions
CloudBeesExternal reviews
635 reviews
from
and
External reviews are not included in the AWS star rating for the product.
My experience with Rollout in production
What do you like best about the product?
This is now my second project I'm using Rollout in (we had three projrct in our devision).
Due to the sucess we had with it in the past, we decided to continuw with this solution for our next projects.
Rollout provides the ability to easily control our features exposure when going to production. The system is relatively easy to use, offers great flexibility with different parameters. We have used it control expose by device, platform, version and more.
The Rollout team also provides great support for questions or issues.
Due to the sucess we had with it in the past, we decided to continuw with this solution for our next projects.
Rollout provides the ability to easily control our features exposure when going to production. The system is relatively easy to use, offers great flexibility with different parameters. We have used it control expose by device, platform, version and more.
The Rollout team also provides great support for questions or issues.
What do you dislike about the product?
There are no real downside for using Rollout.
They offer an SDK for most platforms and allow quick on-boarding.
Adding target groups after project is out there requires code changes to expose more parameters to create those groups on.
They offer an SDK for most platforms and allow quick on-boarding.
Adding target groups after project is out there requires code changes to expose more parameters to create those groups on.
What problems is the product solving and how is that benefiting you?
Gradual exposure of new feature, by platform, version, location, device model and more.Easy to use web dashboard.
Increasing/decreasing our exposure is done very easily and fast now.
Increasing/decreasing our exposure is done very easily and fast now.
Recommendations to others considering the product:
I'm not par of the finence and contract part of the team, but I know that this is a very important part of making the descision.
Try out the system first to understant it and make sure it answers all of your needs.
Understand the limitation and benefits that you get from using this system.
Make sure it fits your platform.
We had limitaion that required Rollout to change/improve their product along the way to support us - platform wise and project wise.
Try out the system first to understant it and make sure it answers all of your needs.
Understand the limitation and benefits that you get from using this system.
Make sure it fits your platform.
We had limitaion that required Rollout to change/improve their product along the way to support us - platform wise and project wise.
Good Experience
What do you like best about the product?
The vast amount of functionality available.
Ease of access and plugin availability to multiple tools.
Dynamic reports and customization to them.
Ease of access and plugin availability to multiple tools.
Dynamic reports and customization to them.
What do you dislike about the product?
The User Interface is a little laggy and not too attractive. But its understandable since it has soo many features.
The functional workflow is a bit lengthy, which can be improved.
The functional workflow is a bit lengthy, which can be improved.
What problems is the product solving and how is that benefiting you?
Automation of release cycle and proper analytics of the releases.
Dashboards help in insights.
Plugins help in combining with multiple tools.
Dashboards help in insights.
Plugins help in combining with multiple tools.
Greet Tool for Release Automation
What do you like best about the product?
We try the community Edition for Release Orchestration for a Proof of Comcept at a customer site.
The interface is very easy to use.and the solution is powerful.
The interface is very easy to use.and the solution is powerful.
What do you dislike about the product?
I dislike the fact that the community edition is not usable in a production environment, even if it is very small.
What problems is the product solving and how is that benefiting you?
An approval workflow of release automation of websphere deployment.
A good tool for controlling app features from outside
What do you like best about the product?
My PO can now disable/enable features when running the app in different environments or doing AB testing, without changing the source code.
Fast and useful support.
Fast and useful support.
What do you dislike about the product?
Marketing team: this was planned for Marketing team to test some experimental features. But they seem to be lazy/busy or afraid of touching technical aspects so they didn't use it.
Dev team: just create their own feature flag variables in the code base, lazy to learn/use rollout for both frontend side and backend side.
Testing: need to be more careful to write unit tests, they shouldn't rely on Rollout feature flags.
Dev team: just create their own feature flag variables in the code base, lazy to learn/use rollout for both frontend side and backend side.
Testing: need to be more careful to write unit tests, they shouldn't rely on Rollout feature flags.
What problems is the product solving and how is that benefiting you?
Rollout makes it easier to manage feature flags in one place.
Recommendations to others considering the product:
* Check Rollout documentation carefully to make sure feature flags are synced correctly.
* Unit test shouldn't be affected by Rollout feature flags.
* Unit test shouldn't be affected by Rollout feature flags.
Great Service, easy to set up, responsive support
What do you like best about the product?
Support is super responsive, I filed a bug and it was resolved around a week later. Also provided helpful answers to my questions.
What do you dislike about the product?
Documentation is sometimes out of date.
What problems is the product solving and how is that benefiting you?
Setting defaults are not as flexible as I'd like.
Recommendations to others considering the product:
Easy way to do remote configuration that can be managed by non-technical users once set up!
Ability to Manage Jenkins Masters with Ease
What do you like best about the product?
The most helpful feature of Cloudbees Core is the ability to remotely manage upgrades, patches, and plugins from a centralized location. We can also pull valuable metrics from the dashboard.
What do you dislike about the product?
There is a need to setup a kubernetes cluster to realizes some of the features.
What problems is the product solving and how is that benefiting you?
We want to be able to manage plugins and upgrades from a centralized location. This helps with maintenance and operation of our build infrastructure.
It solves many problems and opens up new ones
What do you like best about the product?
scale, containerization, and then more characters to satisfy the minimum
What do you dislike about the product?
tracking all the moving parts requires adding more layers of tools/expertise
What problems is the product solving and how is that benefiting you?
ability to scale to properly support our 2000 users
I have had a wonderful experience using Cloudbees Jenkins Core
What do you like best about the product?
Lesser time spent on coding pipelines
Lots of manageable plugins
Lots of manageable plugins
What do you dislike about the product?
UI needs to be improved: offer dashboarding options
What problems is the product solving and how is that benefiting you?
deployment pipelines: its robust, fast and has helped to track issues
CloudBees Core Performance
What do you like best about the product?
I really like the scalability of this application as it is natively build for Kubenetes and uses phemerol agents to build
What do you dislike about the product?
Little complex in understanding operation center when compared to oss jenkins
What problems is the product solving and how is that benefiting you?
Scalabilyt and flexibility
Critical tool for my government customer
What do you like best about the product?
The use of operations center significantly helps with managing multiple Jenkins masters in the development lab.
What do you dislike about the product?
Managing the interdependencies between different versions of plugins is unnecessarily complicated.
What problems is the product solving and how is that benefiting you?
Managing both a development (staging) and production instances of Jenkins masters.
Recommendations to others considering the product:
N/A
showing 251 - 260