CloudBees Unify: Editions
CloudBeesExternal reviews
633 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Cloudbees Core Jenkins CI/CD Automation
What do you like best about the product?
The best part of using Cloudbees Core is the support. The support group is very responsive, and has provided good answers to my requests. They will also help with issues for 3rd party plugins. This is important when pipelines running 24x7.
What do you dislike about the product?
The product can get expensive when scaling for large installations. We currently pay per executor. They offer a per user pricing option with unlimited masters and executors can help, which is more cost effective for organizations with a lot of developers. The pricing model keeps changing so the cost-benefit could improve in the future.
What problems is the product solving and how is that benefiting you?
We are automating our build-test-deploy CI/CD pipelines with Cloudbees CI Core. We have moved from 1 deployment per week to deploying daily. Business is improved due to more secure and tested deployed builds.
Recommendations to others considering the product:
If you are using the free version of Jenkins, I would try Cloudbees Core.
Big solution
What do you like best about the product?
I like the rollout dashboard because is very friendly and the options in the dashboard es good it has many solutions.
The framework or iOS is good because I can install using carthage, the easy configuration using the app delegate is excellent. I can create a customs parameters to configure my variables.
The framework or iOS is good because I can install using carthage, the easy configuration using the app delegate is excellent. I can create a customs parameters to configure my variables.
What do you dislike about the product?
when I use rollout my team founded an error when the connection isn't successful this mean that if rollout not have a connection we can not call to rollout setup or register new flags in execution time.
Rollout is a good solutions to use feature toggling in projects, have any problems like the setup or in the iOS case, the swift version because not have a version history to select the correct carthage version to use in specific project, for example my project run with swift 4.2 because for the company security our computer can not update to last Mac OS version this main that the XCode version that our can use right now is XCode 10.2 but this version isn't compatible with swift 5.0. It was a big problem when I was installing the Rollout framework with my current XCode version.
Rollout is a good solutions to use feature toggling in projects, have any problems like the setup or in the iOS case, the swift version because not have a version history to select the correct carthage version to use in specific project, for example my project run with swift 4.2 because for the company security our computer can not update to last Mac OS version this main that the XCode version that our can use right now is XCode 10.2 but this version isn't compatible with swift 5.0. It was a big problem when I was installing the Rollout framework with my current XCode version.
What problems is the product solving and how is that benefiting you?
The benefits with Rollout is the best management of the features in an application. The Rollout dashboard help me to setup my project using common values and the best is that I can create a customs parameters to configure my variables.
Recommendations to others considering the product:
Fix problem when rollout can not make a connection.
Rollout Review
What do you like best about the product?
Program is easy to use and has metrics to accurately display how our features are being released.
What do you dislike about the product?
Unclear what users have access to different features when using the Split function. Not sure if this is intentional or I'm not seeing it but it would be helpful to see what users have a feature during the experiment.
What problems is the product solving and how is that benefiting you?
Having the ability to properly beta test different features. We have
CloudBees Flow (Electric Cloud Flow) best Release Automation tool
What do you like best about the product?
CloudBees Flow is the best Release Automation tool that exist in the market. From the best features is the possibility to define Environment for an application and next define a pipeline to promote artifacts.
The next thing is you can define your workflow as code using a specific DSL.
The next thing is you can define your workflow as code using a specific DSL.
What do you dislike about the product?
The UI is a little complexe and hard to decipher from the first usage, also defining the pipeline and the workflow can be a tedious task from the UI. This from my own usage experience, because I use it for evaluation propose only.
What problems is the product solving and how is that benefiting you?
- Build Promotion, possibility to promote a build to production if tests are successful in staging.
- Gather analytics and data about the release process.
- Integration with many other deployments tools like Ansible
- Gather analytics and data about the release process.
- Integration with many other deployments tools like Ansible
Recommendations to others considering the product:
best release automation and management tool
Great platform for feature management
What do you like best about the product?
Ease of use, good analytics model which allows great insights to support business calls
What do you dislike about the product?
It is missing an on-prem solution thus it prevents some companies
What problems is the product solving and how is that benefiting you?
Instead of working with ugly and non-managable json files, working with the ROX SDK is really great.
Microservice deployment pipeline
What do you like best about the product?
CloudBees Flow provides feature rich software and platform for an automated software deployment
What do you dislike about the product?
I would like to see more documentation on how to write DSL. There are tutorials to use CloudBees UI to create pipeline but for the professional work, we need to write the deployment scripts as code and store them in repo. The information on the DSL part seems lacking.
What problems is the product solving and how is that benefiting you?
My company is moving into fully automated software deployments using CloudBees. Currently a lot of teams still practices manual deployment or partially automated scripts for a specific environment such as DEV, STG or PROD. CloudBees Flow provides solution for a single pipeline from DEV, to STG, to PROD.
My experience with Rollout in production
What do you like best about the product?
This is now my second project I'm using Rollout in (we had three projrct in our devision).
Due to the sucess we had with it in the past, we decided to continuw with this solution for our next projects.
Rollout provides the ability to easily control our features exposure when going to production. The system is relatively easy to use, offers great flexibility with different parameters. We have used it control expose by device, platform, version and more.
The Rollout team also provides great support for questions or issues.
Due to the sucess we had with it in the past, we decided to continuw with this solution for our next projects.
Rollout provides the ability to easily control our features exposure when going to production. The system is relatively easy to use, offers great flexibility with different parameters. We have used it control expose by device, platform, version and more.
The Rollout team also provides great support for questions or issues.
What do you dislike about the product?
There are no real downside for using Rollout.
They offer an SDK for most platforms and allow quick on-boarding.
Adding target groups after project is out there requires code changes to expose more parameters to create those groups on.
They offer an SDK for most platforms and allow quick on-boarding.
Adding target groups after project is out there requires code changes to expose more parameters to create those groups on.
What problems is the product solving and how is that benefiting you?
Gradual exposure of new feature, by platform, version, location, device model and more.Easy to use web dashboard.
Increasing/decreasing our exposure is done very easily and fast now.
Increasing/decreasing our exposure is done very easily and fast now.
Recommendations to others considering the product:
I'm not par of the finence and contract part of the team, but I know that this is a very important part of making the descision.
Try out the system first to understant it and make sure it answers all of your needs.
Understand the limitation and benefits that you get from using this system.
Make sure it fits your platform.
We had limitaion that required Rollout to change/improve their product along the way to support us - platform wise and project wise.
Try out the system first to understant it and make sure it answers all of your needs.
Understand the limitation and benefits that you get from using this system.
Make sure it fits your platform.
We had limitaion that required Rollout to change/improve their product along the way to support us - platform wise and project wise.
Good Experience
What do you like best about the product?
The vast amount of functionality available.
Ease of access and plugin availability to multiple tools.
Dynamic reports and customization to them.
Ease of access and plugin availability to multiple tools.
Dynamic reports and customization to them.
What do you dislike about the product?
The User Interface is a little laggy and not too attractive. But its understandable since it has soo many features.
The functional workflow is a bit lengthy, which can be improved.
The functional workflow is a bit lengthy, which can be improved.
What problems is the product solving and how is that benefiting you?
Automation of release cycle and proper analytics of the releases.
Dashboards help in insights.
Plugins help in combining with multiple tools.
Dashboards help in insights.
Plugins help in combining with multiple tools.
Greet Tool for Release Automation
What do you like best about the product?
We try the community Edition for Release Orchestration for a Proof of Comcept at a customer site.
The interface is very easy to use.and the solution is powerful.
The interface is very easy to use.and the solution is powerful.
What do you dislike about the product?
I dislike the fact that the community edition is not usable in a production environment, even if it is very small.
What problems is the product solving and how is that benefiting you?
An approval workflow of release automation of websphere deployment.
A good tool for controlling app features from outside
What do you like best about the product?
My PO can now disable/enable features when running the app in different environments or doing AB testing, without changing the source code.
Fast and useful support.
Fast and useful support.
What do you dislike about the product?
Marketing team: this was planned for Marketing team to test some experimental features. But they seem to be lazy/busy or afraid of touching technical aspects so they didn't use it.
Dev team: just create their own feature flag variables in the code base, lazy to learn/use rollout for both frontend side and backend side.
Testing: need to be more careful to write unit tests, they shouldn't rely on Rollout feature flags.
Dev team: just create their own feature flag variables in the code base, lazy to learn/use rollout for both frontend side and backend side.
Testing: need to be more careful to write unit tests, they shouldn't rely on Rollout feature flags.
What problems is the product solving and how is that benefiting you?
Rollout makes it easier to manage feature flags in one place.
Recommendations to others considering the product:
* Check Rollout documentation carefully to make sure feature flags are synced correctly.
* Unit test shouldn't be affected by Rollout feature flags.
* Unit test shouldn't be affected by Rollout feature flags.
showing 241 - 250