External reviews
External reviews are not included in the AWS star rating for the product.
Powerful feature flags with all the integrations we need
What do you like best about the product?
I love that it works with React Native and integrates with Jira. These were our must-haves for a feature flagging tool. It was simple to get it up and running and it does everything we need it to.
What do you dislike about the product?
So far I’ve been unable to find a way to make feature flags change in RN without reloading - but this is a minor detail.
What problems is the product solving and how is that benefiting you?
We are able to release code to production environments and gradually enable new features - measuring impact before releasing them generally.
Recommendations to others considering the product:
Definitely worth investigating if you use React Native
- Leave a Comment |
- Mark review as helpful
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.
Very customizable, but also very time consuming to maintain
What do you like best about the product?
Shared libraries, that allow us to create one Pipeline that is used by multiple projects of the same type. Our previous engine didn't allow this and when we needed to introduce a change to the delivery process, we had to update hundreds of pipelines manually. This goes away with Shared libraries.
What do you dislike about the product?
Maintenance burden is a hell. You need an engineer full time to keep an eye on updates of the products, updates of the plugins, making sure all the used plugins are still compatible (in case they fall into community tier), and all the setup and maintenance that comes with a product that you host yourself (infrastructure maintenance and updates, pagerduty setup, proper guidelines for support of internal teams using the product...etc).
What problems is the product solving and how is that benefiting you?
At the moment, we have problems with underlying kubernetes infrastructure - we're still tuning what is the right memory setup, number of pods per team, what their size should be, etc. Also, there are some plugins (proprietary, developed by CloudBees), which has bugs that make them impossible to use in larger scale.
Usually their support is quite helpful, but sometimes, they will tell you - this is infrastructure, you need to deal with it yourself. Which sometimes is true, but sometimes would be nice to provide couple of hints or articles about how to do that, especially if you don't have years of experience with kubernetes, docker and AWS EKS (this is our setup).
The benefit of using CloudBees compare to using Jenkins for sure is the Operations Center which allow nice Cluster management (restarts and updates of all the connected masters at once).
On the down side, even though are masters (the ones that execute the actual jobs) are the same, they behave quite stochastic and require large deal of troubleshooting during maintenance windows (sometimes they bet stuck at unready status, sometimes they time out on attaching persistent volumes...etc).
Usually their support is quite helpful, but sometimes, they will tell you - this is infrastructure, you need to deal with it yourself. Which sometimes is true, but sometimes would be nice to provide couple of hints or articles about how to do that, especially if you don't have years of experience with kubernetes, docker and AWS EKS (this is our setup).
The benefit of using CloudBees compare to using Jenkins for sure is the Operations Center which allow nice Cluster management (restarts and updates of all the connected masters at once).
On the down side, even though are masters (the ones that execute the actual jobs) are the same, they behave quite stochastic and require large deal of troubleshooting during maintenance windows (sometimes they bet stuck at unready status, sometimes they time out on attaching persistent volumes...etc).
Recommendations to others considering the product:
If you consider purchasing CloudBees yourself, make sure you have enough capacity to carry on the related maintenance burden. Also that the team has enough experience with the underlying infrastructure. If not, rather look at SaaS solutions like Jfrog Pipelines or CircleCI.
One of the Best Product
What do you like best about the product?
This is one of the greatest product in the industry. I love their idea totally. I love if they continue to add more plugins to integrate with upcoming tools in the market. We are using Jenkins in different environments. We recommend this product to make a use of their options available. Because Jenkin can
What do you dislike about the product?
Nothing much, as far I can see they are continue to develop everyday.
What problems is the product solving and how is that benefiting you?
All of our development teams using Jenkins. We are solving our micro service application integration issues.
Recommendations to others considering the product:
No other products can catch some of the ideas that available in Jenkins.
Cloudbees Jenkins CI
What do you like best about the product?
Ability to Integrate with most of the 3rd part tools. Easily accessible UI and great and quick support.
What do you dislike about the product?
Community driven plugins where we have minimal support. It would be good if cloudbees can provide own plugins with good support.
What problems is the product solving and how is that benefiting you?
Improved efficiency of build and test automation. Saved time and resources with distributed parallel and sequential builds.
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
Senior Devops Engineer.
What do you like best about the product?
Prompt support.
Stable tool.
Frequent updates
Stable tool.
Frequent updates
What do you dislike about the product?
Little difficult to manage , learn for new
What problems is the product solving and how is that benefiting you?
Stable enterprise environment.
showing 331 - 340