Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the 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
- Leave a Comment |
- Mark review as helpful
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.
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
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.
showing 331 - 340