CloudBees Unify: Editions
CloudBeesExternal reviews
635 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Powerful Application Development System.
What do you like best about the product?
The online support its perfect and helpful, and myself i love how the user can simply deploy either everything or even some of artifacts in a given Application and the easy of usage.
CloudBees CD can effectively support various software development teams working from different places, and simple to share Applications.
CloudBees CD can effectively support various software development teams working from different places, and simple to share Applications.
What do you dislike about the product?
No issues with the CloudBees CD functionalities, easy and flexible functions to get used to their functionality.
What problems is the product solving and how is that benefiting you?
Easy Application deployment and also Application sharing among other different usage depending with the project.
Recommendations to others considering the product:
Excellent solution for the easy software deployment and easy on sharing various thing like Automation and easy dashboard to navigate.
Support staff of CloudBees is so experienced!
What do you like best about the product?
The support personnel of CloudBees are highly trained and experienced. They typically fill in the gaps in plugins and documentation of the Jenkins, especially if Java programmers are not people who try to use them. It is also hard to discern where exactly they go. But I may ask someone for a fast answer in case I have a request. I love your attention to detail step by step by step.
What do you dislike about the product?
Often there is no documentation, e.g. where you can check for an update or how a particular folder can be handled.
What problems is the product solving and how is that benefiting you?
I have added the particular software to guarantee that the workers have the same capacities as our primary Jenkins installation when combined with another Jenkins installation. Cjs provided me with plugins that I would have to instal and then helped me organise the actual upgrade steps, ensuring that I would be able to back up a plan if the update was random and inconsistent.
Recommendations to others considering the product:
It is worth purchasing a service agreement if you have your own Jenkins-server and use it for critical functions. You will save the agony of tomorrow by the dollars you consume today.
The pipeline plugin is a must-have!
What do you like best about the product?
The capacity to add several plugins that make space for a lot of applications. The primary thing that tends to make creating configuration management pretty managementable is the Pipeline wordpress plugin with share libraries. We are able to develop some really advanced pipelines with the blend of declarative and scripted pipelines involving and control a variety of various other plugins, control them resource and also share them effortlessly. The capacity to add customised plugins is excellent for providing specific solutions.
What do you dislike about the product?
The interface lacks visual interest, as well as often it's challenging as well as easy to alter pipeline setup out of the user interface. Blue Ocean is a beautiful pipeline visualisation, but it's numerous custom functions and it is significantly less consumer friendly as intended.
What problems is the product solving and how is that benefiting you?
The benefit of pipelines that comes with shared libraries is astounding in dealing with numerous build configurations utilizing Pipeline plugin. with the multi branch pipeline plugin, we are able to develop a variety of tasks with a click. Mixed utilization of a declarative and also script pipeline lets us very easily share configurations with just so much data to share.
Recommendations to others considering the product:
It is able to truly be used for the use and several projects of the plug in pipeline suite causes it to be super easy to control and show others, that can review configuration changes as well as perform unit trials. There's a big plus in the choice for incorporating nodes and straightforward deletion of nodes with no licencing on many OSes.
It minimizes dramatically the risks of production rollouts.
What do you like best about the product?
Simplicity. The UI/Engine is simple to comprehend and use.
What do you dislike about the product?
Honestly, the app is good for my needs, except that the price is something that causes challenges when convincing the executives to go for it.
More documentation to help on the feature flags management, like cleanup process, etc. would be helpful.
More documentation to help on the feature flags management, like cleanup process, etc. would be helpful.
What problems is the product solving and how is that benefiting you?
Prevent unnecessary risks of hitting production. The team/management is way more comfortable when pushing code to production.
It also expedited our time to production.
It also expedited our time to production.
Recommendations to others considering the product:
Definitely a must if your business is growing and requires less time to market.
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.
showing 171 - 180