External reviews
External reviews are not included in the AWS star rating for the product.
Love it thanks to the last ui update! Made a huge difference!
What do you like best about the product?
The analytics and the simplicity. The option to use complex conditions like using target groups etc.
What do you dislike about the product?
The time it takes to load pages.
I think it would be great if there was an option of some kind of an automatic reminder for removing old feature flags.
I think it would be great if there was an option of some kind of an automatic reminder for removing old feature flags.
What problems is the product solving and how is that benefiting you?
It is a simple way to use complex and temporary configuration variables.
It is well organized and divided by environments.
It is well organized and divided by environments.
Recommendations to others considering the product:
Nice product, simple to configure and use.
- Leave a Comment |
- Mark review as helpful
We love CloudBees Feature Flags, we wouldn't have reached continues deployment with out it
What do you like best about the product?
1) Easy integration into our code base (nodejs).
2) Lot of flexibility in the way we define experiments - we use different attributes on user and environment in order to decide if we want to open a feature flag or not.
3) Ability to control environments easily - we have multiple environments and the ability to add new environments easily is really helpful.
4) Really competitive pricing - We did a POC with launch darkly and ended up moving to CloudBees Feature Flags partially due to pricing issues.
5) Performance - we were afraid using CloudBees Feature Flags will result in performance issues but ended up really happy with the result. We didn't feel a a major impact on our performance
2) Lot of flexibility in the way we define experiments - we use different attributes on user and environment in order to decide if we want to open a feature flag or not.
3) Ability to control environments easily - we have multiple environments and the ability to add new environments easily is really helpful.
4) Really competitive pricing - We did a POC with launch darkly and ended up moving to CloudBees Feature Flags partially due to pricing issues.
5) Performance - we were afraid using CloudBees Feature Flags will result in performance issues but ended up really happy with the result. We didn't feel a a major impact on our performance
What do you dislike about the product?
Missing configuration management capabilities - I know this is not part of product but I think it could be really easy to use the infra to add one.
Control features as part of Continues Deployment cycle - we want our feature flags to roll be default between different environments. Easy integration into our SDLC could be really helpful.
Control features as part of Continues Deployment cycle - we want our feature flags to roll be default between different environments. Easy integration into our SDLC could be really helpful.
What problems is the product solving and how is that benefiting you?
We use CloudBees Feature Flags to allow gradual release of our features. It has helped us move our deployment cycle from once a week to once a day pushing us towards continues delivery.
We also use Cloudbees Feature Flags for configuration management. Our platform is multi tenant and we sometimes use the product to define different configuration for different use type or tenants
We also use Cloudbees Feature Flags for configuration management. Our platform is multi tenant and we sometimes use the product to define different configuration for different use type or tenants
Ease of configuration, instant update and non-developer friendly
What do you like best about the product?
Easy to set up target audience per flag and being able to have defined target groups. I also noticed some recent UI updates and it looks much better now!
The impressions are also helpful to know how many users have the updated app to help us see how many users have a feature enabled/disabled.
Minor UI bug: flag settings tab has a bottom margin/padding issue :)
The impressions are also helpful to know how many users have the updated app to help us see how many users have a feature enabled/disabled.
Minor UI bug: flag settings tab has a bottom margin/padding issue :)
What do you dislike about the product?
We have had some troubles with Python integration. I can't recollect the exact details but it had not been possible to use it in our backend. It works smoothly for our frontend though
What problems is the product solving and how is that benefiting you?
We had a configuration file in our code that was managing list of alpha, beta users and different experiment checks. It was a pain to update and deploy every time we wanted to test something. We switched to Rollout so we could have that configuration outside the code. That way our non-dev team members can also use the UI to release features to the correct target audiences. We can also easily toggle a feature on and off if a particular customer wishes to try it out
Fast & reliable!
What do you like best about the product?
- Updates are sent quickly
- Easy to implement
- Dashboard easy to understand
- Easy to implement
- Dashboard easy to understand
What do you dislike about the product?
- maybe the price
- sdks may be updated (kotlin for android)
- sdks may be updated (kotlin for android)
What problems is the product solving and how is that benefiting you?
Having real time flags inside our apps to give fast insights to our users & see the impact on them. Also, a/b tests (not tested yet)
Great and intuitive Feature Flags platform
What do you like best about the product?
Really easy to setup, use and configure.
What do you dislike about the product?
More inline help would have been great when editing experiments
What problems is the product solving and how is that benefiting you?
Running various experiments against a group of users. CloudBees Feature Flags allowed me to perform such task pretty quickly.
Recommendations to others considering the product:
Great product.
Its handy but has issues with sync
What do you like best about the product?
easy to use and nice UI its also has many possibilities
What do you dislike about the product?
Some times when i update FF i think it's was updated but the only refresh will show the real state
What problems is the product solving and how is that benefiting you?
Also setting for an environment that controlled with API keys
A robust enterprise-ready Jenkins implementation!
What do you like best about the product?
Operations Center lets us easily manage multiple masters via one interface, Cluster operations for upgrades and plugin management. Templates help us enforce and maintain best practices across the enterprise (internal and 3rd party teams). We can onboard new projects and teams quickly, via a pre-configured security model available out of the box that supports single sign on. Role-based access controls allow for finer control of access to pipelines and jobs. Support for elastically scalable infrastructure and modern, cloud-native implementation (via Jenkins X). CloudBees Network for team self-service troubleshooting.
What do you dislike about the product?
Quite complicated pricing strategy until a few months ago, that CloudBees is reviewing it and has improved. Lack of customization options for user profile. It'd be really helpful to have a broader support for non-official plugins (but it's constantly adding more and more).
What problems is the product solving and how is that benefiting you?
The main benefit is the ability to remove the usual single-point-of-failure-approach of having a monolithic, shared, huge and expensive Jenkins master when trying to bring governance and security best practices. This is because with CloudBees CI each team might its own appropriately-sized and configured master (and agents), and also follow the security and governance guidelines enforced by the templates and CJOC. This solves most of the usual firefighting when a team messes with the configuration and affects all our software shop, helping our teams to stay productive and limit the impact of any problem found.
Very usable service
What do you like best about the product?
Simple configuration, and lots of analytics
What do you dislike about the product?
CloudBees is a very expensive service and there are other service more cheaper
What problems is the product solving and how is that benefiting you?
We use feature flag on any feature developed by client or backend
Im using rollout to handle feature flags in server and client side
What do you like best about the product?
easy concept,
nice upgrade of the ui, allows me to handle turning on features with ease and controlling when to publish them
nice upgrade of the ui, allows me to handle turning on features with ease and controlling when to publish them
What do you dislike about the product?
rollout client bundle size is big! (rox-browser)
it was huge but they did some work to reduce it (from 300kb to 150kb), in my opinion there is more work to be done with reducing it
new admin ui load times are bad..
takes about a minute or so until the flags are actually updated
it was huge but they did some work to reduce it (from 300kb to 150kb), in my opinion there is more work to be done with reducing it
new admin ui load times are bad..
takes about a minute or so until the flags are actually updated
What problems is the product solving and how is that benefiting you?
deploying code in a hidden way so we will be able to test it before it's ready for production and once it's ready open the feature in production
Recommendations to others considering the product:
be sure to use the latest version if you're integrating it in your browser as the newer versions have better bundle size
Cloudbees Core CI is good to automatize stuff
What do you like best about the product?
Variety of plugins proposed in the catalog. The client service which is very reactive. I love that they integrated their new Cloudbees CI in the Kubernetes environment.
I also love the shared libraries feature, which permits to have a common code base of groovy functions for all Cloudbees CI users in the organization. Indeed, this feature permits to push development standards in the organization.
I also love the fact that you can create Jenkins Team masters for development teams. It gives them more autonomy on settings in their Team.
Cloudbees CI also permits developers to have a "click to deploy" pipeline. It also helps developers to be more autonomous about their Product life cycle.
I also love the shared libraries feature, which permits to have a common code base of groovy functions for all Cloudbees CI users in the organization. Indeed, this feature permits to push development standards in the organization.
I also love the fact that you can create Jenkins Team masters for development teams. It gives them more autonomy on settings in their Team.
Cloudbees CI also permits developers to have a "click to deploy" pipeline. It also helps developers to be more autonomous about their Product life cycle.
What do you dislike about the product?
The Graphical User interface is very poor, the outdated plugins. Sometimes, the logs are very hard to find. For example, when you have a problem of a Kubernetes pod which doesn't want
Another thing I don't like about Cloudbees CI is the fact that it is so hard to debug pipelines : sometimes, the stack trace in the console output is really hard to interpret and has merely nothing in link to the real issue that is occuring.
I don't like the fact that there are no APIs exposed which we can use to trigger Cloudbees CI actions.
I also don't like the documentation on installing Cloudbees CI in the cloud. It requires to install it with Helm whereas another installation is possible by just using Kubernetes Objects Yaml Templates.
Another thing I don't like about Cloudbees CI is the fact that it is so hard to debug pipelines : sometimes, the stack trace in the console output is really hard to interpret and has merely nothing in link to the real issue that is occuring.
I don't like the fact that there are no APIs exposed which we can use to trigger Cloudbees CI actions.
I also don't like the documentation on installing Cloudbees CI in the cloud. It requires to install it with Helm whereas another installation is possible by just using Kubernetes Objects Yaml Templates.
What problems is the product solving and how is that benefiting you?
Creating standard pipelines for java, python and Node JS which build code and deploy on VM or containers using Ansible or Kubernetes.
Recommendations to others considering the product:
You should definitely give Tekton a try. Indeed it is great to use in a Kubernetes context.
showing 321 - 330