CloudBees Unify: Editions
CloudBeesExternal reviews
633 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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
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.
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.
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.
Smooth integration with xaaf project
What do you like best about the product?
Can easy use different context for determining feature flag value, without having to reload or fetch to server.
What do you dislike about the product?
Can't discard and setup sdk again with different api key.
What problems is the product solving and how is that benefiting you?
Enabling and disabling features. Wrapping risky features with FF lets us be more confident in shipping out to production, and giving us the ability to tweak without changing code.
Reporting can be wrapped with Feature flags to limit the amount of reporting, while using context to spread out to different users.
Reporting can be wrapped with Feature flags to limit the amount of reporting, while using context to spread out to different users.
Great, simple feature flag service
What do you like best about the product?
Cloudbees has a very non-cluttered UI that makes all feature flags, and their value, very visable
What do you dislike about the product?
We ran into some integration issues with cloudbees and datadog that we had to figure out
What problems is the product solving and how is that benefiting you?
We turn off/on certain features and flows of our service using flags
Feature Flagging- mostly good
What do you like best about the product?
The tool is easy to use and works! Once implemented we came to rely on it heavily
What do you dislike about the product?
I've had issues adding a lot of conditions to a target group, creating multiple target groups has gotten around this. Also there isn't an obvious/easy way to import or export things like conditions which creates work.
What problems is the product solving and how is that benefiting you?
I use CloudBees to do controlled feature pilots and tests. This has made the feature rollout process much easier.
Recommendations to others considering the product:
CloudBees is great. It works well and is easy to implement and use.
Probably the most comprehensive & powerful CI offer on the market
What do you like best about the product?
1. Ability to manage and supervise a host of Jenkins masters in a centralised manner and allocate a dedicated Jenkins instance to each individual development team
2. Ability to leverage the benefits of running on a Kubernetes cluster and still handle legacy instances on traditional virtual machines. This includes the ability to use Helm charts for installation, Ansible scripts for infrastructure as code, and the ability to create build agents as pods
3. Extensive features to handle authentication and authorizations with LDAP/AD groups
2. Ability to leverage the benefits of running on a Kubernetes cluster and still handle legacy instances on traditional virtual machines. This includes the ability to use Helm charts for installation, Ansible scripts for infrastructure as code, and the ability to create build agents as pods
3. Extensive features to handle authentication and authorizations with LDAP/AD groups
What do you dislike about the product?
1. The features around Teams are a bit hard to get into, and apparently access to Teams Jenkins instances require you to log in through the Operations Center (CJOC) instance.
2. Overall, the learning curve can be a bit steep, therefore it is advisable to get onboarding/training through Cloudbees Professional Services.
3. The user/licence count system is a bit obscure. At present we still don't have a clear view as to what constiutes a "user" for the CLoudbees licence. We assume a user is an individual account that has access to at least one of the Jenkins instances deployed, but it looks like CLoudbees may actually consider that any individual having commited code that is accessed through a Jenkins job may count as a user. In the latter case, it would of course be totally unfair and we would dispute this but so far we haven't got a clear view on the matter.
4. Creating a new CJOC instance requires you to get an instance Id through Cloudbees support. It would be preferable if this was a one-off process for all instances
2. Overall, the learning curve can be a bit steep, therefore it is advisable to get onboarding/training through Cloudbees Professional Services.
3. The user/licence count system is a bit obscure. At present we still don't have a clear view as to what constiutes a "user" for the CLoudbees licence. We assume a user is an individual account that has access to at least one of the Jenkins instances deployed, but it looks like CLoudbees may actually consider that any individual having commited code that is accessed through a Jenkins job may count as a user. In the latter case, it would of course be totally unfair and we would dispute this but so far we haven't got a clear view on the matter.
4. Creating a new CJOC instance requires you to get an instance Id through Cloudbees support. It would be preferable if this was a one-off process for all instances
What problems is the product solving and how is that benefiting you?
We are trying to solve scalability and manageability problems we have been experiencing since we only had a central, "éfederal" Jenkins isntance consisting of a single master and half a dozen agents.
Also, we were planning to move to a modern Kubernetes environment to benefit from all the features in terms of 'elastic' computing, fault tolerance and supervision.
FInally, we needed a better auhorization & group management system than the basic features including in open-source Jenkins.
Also, we were planning to move to a modern Kubernetes environment to benefit from all the features in terms of 'elastic' computing, fault tolerance and supervision.
FInally, we needed a better auhorization & group management system than the basic features including in open-source Jenkins.
Recommendations to others considering the product:
Excellent commercial and technical support and very good training.
Wonderful tool to work in CI
What do you like best about the product?
The user experience and the customer support was excellent
What do you dislike about the product?
There is nothing which i didn't like. All good
What problems is the product solving and how is that benefiting you?
Helped in automation of builds and quick feedback
Recommendations to others considering the product:
None so far
showing 171 - 180