CloudBees Unify: Editions
CloudBeesExternal reviews
635 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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
Great extensions on top of open source Jenkins
What do you like best about the product?
If you can gain access to the "fancy Jenkins" there are a lot of little quality of life improvements that are really nice, as well as a few bigger pieces like potential for deeper analytics. It is a Jenkins with more Jenkins in it (literally, in the case of the master-of-masters). And the installation leaves you with a really nicely prepared instance, including a Kubernetes agent cloud - although the Jenkins Kubernetes Operator is catching up to some degree there.
What do you dislike about the product?
Not much to dislike other than the pricing ;-)
What problems is the product solving and how is that benefiting you?
Maybe the biggest benefit is the ease of creating new Jenkins masters for new teams, while centralizing config in the master-of-masters, for whatever you want to control globally. User auth is probably the best example of that, and can be cascaded out to all masters. No more having to hand-configure every master separately!
Easy to Use with Less Configuration Workload
What do you like best about the product?
CloudBees CI is easy and direct way to make application deployed in on-premise or hosted on a cloud service provider without doing much of configuration change in underline infrastructure. The user interface is intutive to on-board users. With the emergence of adapting to CloudNative solution for using K8S cluster with good user interface.
What do you dislike about the product?
Nothing specific to complain or dislike as I am new and exploring the product for my personal knowledge
What problems is the product solving and how is that benefiting you?
Centralized tool for most of the Devops pipeline and delivery system with dashboard for generating data metrics for analysis and audit report
Recommendations to others considering the product:
Yes as the product offers a centralized tool for your Devops pipeline and delivery system which can be an integral part of Digital Transformation
The best enterprise CI out there!
What do you like best about the product?
Integrations present in Cloudbees CI are the best, along with the Test customizations it provides.
The entire UI of the CI is well crafted compared to the other CI tools.
The entire UI of the CI is well crafted compared to the other CI tools.
What do you dislike about the product?
Nothing to dislike as such at the moment & I hope it stays that way!
What problems is the product solving and how is that benefiting you?
My day to day code integrations used to be a pain!
Since switching to CloudBees CI, it's been a relief to automate the CI/CD,
Since switching to CloudBees CI, it's been a relief to automate the CI/CD,
The most convenient scalable solution to release, with a fallback in place!
What do you like best about the product?
It is the most critical functionality in the Agile world.
It helps to reduce the risks during feature releases and product deployments and also makes the system less error-prone.
It guarantees a fallback mechanism and ensures safety within the team.
This increases the scope of productivity among developers and testers, to build and deploy the changes with confidence.
It is build with keeping non-technical users in mind, which means anyone having knowledge in this regard can go ahead and release or rollback the changes with a simple toggle like feature flag.
It gives extreme control to everyone working on the feature across the system, making it very simple and intuitive.
It helps to reduce the risks during feature releases and product deployments and also makes the system less error-prone.
It guarantees a fallback mechanism and ensures safety within the team.
This increases the scope of productivity among developers and testers, to build and deploy the changes with confidence.
It is build with keeping non-technical users in mind, which means anyone having knowledge in this regard can go ahead and release or rollback the changes with a simple toggle like feature flag.
It gives extreme control to everyone working on the feature across the system, making it very simple and intuitive.
What do you dislike about the product?
It increases the testing time a bit and need to double confident that the feature would rollback correctly, completely depending on how the feature flag has been implemented within the system
What problems is the product solving and how is that benefiting you?
We can deliver our features in a more Agile manner.
There is an increase in confidence and improved productivity with the mindset of feature flag.
The rollbacks and release process seem more simplified, making it the most preferable solution moving forward.
There is an increase in confidence and improved productivity with the mindset of feature flag.
The rollbacks and release process seem more simplified, making it the most preferable solution moving forward.
Recommendations to others considering the product:
Very useful as it fastens the release process thus improving the Continuous Integration and Continuous Delivery
Cloudbees Jenkins - Just another tool ??
What do you like best about the product?
Seamless integration with other tools and technologies
What do you dislike about the product?
no native kubernetes deployment strategy
What problems is the product solving and how is that benefiting you?
we build our CI pipelines using Cloubees Jenkins. Both groovy pipelines as well as freestyle
Its the supported industry standard
What do you like best about the product?
Besides cloudbee support there's tons of support on SO and others
What do you dislike about the product?
The wide variety of plugins and rate of change can mean there's out of date documentation or plugins that aren't that great
What problems is the product solving and how is that benefiting you?
Platform that can support any type of workload you can come up with
showing 181 - 190