External reviews
External reviews are not included in the AWS star rating for the product.
Cloudbees CI has good plugin support and configurability.
What do you like best about the product?
Most 3rd party tools are supported usually via a plugin. Documentation on cloudbees is really good.
What do you dislike about the product?
It's sometimes hard to diagnose build failures. We see often see networking problems when agent disconnections. It's hard to manage large number of plugin versions.
What problems is the product solving and how is that benefiting you?
It's good for creating automation and building source code and pushing to repositories.
- Leave a Comment |
- Mark review as helpful
An easy CI to learn and implement complex networks of builds
What do you like best about the product?
The ability to add multiple plugins that make room for so many use-cases. Most importantly the Pipeline plugin with shared libraries makes builds configuration management quite manageable. With a mix of declarative and scripted pipeline, we can create some really complex pipelines that make use of several other plugins and still be able to manage them, source control them and share with ease. The ability to add custom plugins is great to be able to cater some personalized solutions.
What do you dislike about the product?
The UI lacks visual appeal, and editing pipeline configurations from the UI is still not easy and even possible in some cases. Blue Ocean is a nice visualization of the pipeline but it lacks many custom features and is not as easy to use as projected. Multiple pipeline builds running on the server makes memory management bit of an issue. Not many customization options for user profile. Needs to be updated for modern color scheme and design.
What problems is the product solving and how is that benefiting you?
Managing multiple build configurations using the Pipeline plugin, the benefit of Pipelines coupled with shared libraries is immense. The multi-branch pipeline plugin allows us to create multiple jobs for different branches with a click. Combined use of declarative and scripted pipeline helps us share build configurations easily with only as much information needed to be shared. Shared libraries are really powerful to use in almost all of our pipelines due to the fact that they are so lightweight.
Recommendations to others considering the product:
It can really scale for multiple projects and the use of Pipeline suite of plugins makes it very manageable and shareable with others that can review the configuration changes and also run unit tests on them. The option to add nodes and remove nodes easily without having to license any on majority of the OSes out there is a huge plus.
Cloudbees CI review
What do you like best about the product?
We are using the open-source. docker image for Cloudbee's Jenkins distribution, and like the regular updates, testing and all work going into such an offering.
What do you dislike about the product?
As we need to maintain a multi-master setup, it would be great to include features for that in the open-source version as well.
What problems is the product solving and how is that benefiting you?
We are building all our software with it. Jenkins pipelines and pipeline libraries are a great way to uniformly build our python packages and services.
Great upgrade to an already excellent product
What do you like best about the product?
I've used open source Jenkins and CloudBees Jenkins Platform prior to using CloudBees CI. Each new iteration was better than the last. The old license model was based on the number of masters and agents which was extremely limiting. We had 2 masters and 10 executors shared across them. Near the release date, the system became extremely busy which lead to increases in build times due to waiting. The main benefit of CloudBees CI is infinite master and agent scaling due to the change in license structure. This allows many teams to use and manage their own system. Since each master connects to the operations center, onboarding time is decreased since the new masters can reuse existing configurations provided by the operations center.
What do you dislike about the product?
So far there are not many downsides to using CloudBees CI. It seems like the user based licensing is slightly more expensive. Also managing or paying for Kubernetes infrastructure can be costly but this is where most of the scalability of the platform comes from.
What problems is the product solving and how is that benefiting you?
CloudBees CI allows us to unify the Jenkins infrastructure that many of our teams use. Instead of each team running their own open source master and agents they can now take advantage of the features of CloudBees CI. The new licensing also assists with scaling our infrastructure as we need to grow.
Recommendations to others considering the product:
CloudBees CI offers many integrations which makes it useful. Consider the cost of migrating and using more of the plugins versus a scripted approach.
Easy and Reliable CI tool
What do you like best about the product?
Its easy to manage kubernates pods and Docker deployment using this.Improves overall build automation process and validation easy . Support from cloudbees team is really good. It is a cloud native solution for CI.
What do you dislike about the product?
They need to upgrade application's User Interface
What problems is the product solving and how is that benefiting you?
We are trying to solve CI problems using cloud-bees. Its easy to used and provides multiple integration points
CloudBees fixes all the things you hate about Jenkins
What do you like best about the product?
Plugins are the best and worst part of Jenkins. They are the real power of customizing your pipeline but with weekly updates and different schedule they keep breaking.
CloudBees fixes that issue by bundling up all plugin update quarterly and testing them. This remove all the complexity and downtime of keeping Jenkins up to date.
CloudBees fixes that issue by bundling up all plugin update quarterly and testing them. This remove all the complexity and downtime of keeping Jenkins up to date.
What do you dislike about the product?
I wish CloudBees would have a full SAAS solution. It requires that you deploy it to your own cloud environment which still take some unneeded complexity and maintenance.
What problems is the product solving and how is that benefiting you?
Week long updates and fixes are now minutes.
Setup cloudbees CI on Openshift cluster
What do you like best about the product?
I have deployed Cloudbees CI on openshift and it provides lots of facility to create your own managed master and manage them in operation center.This is very user friendly with enrich capability of CI-CD
What do you dislike about the product?
i am not sure for dislike at this moment
What problems is the product solving and how is that benefiting you?
It solves the CI/CD implementation of application development process.
Does not work well with kubernetes
What do you like best about the product?
Ability to re-use in-house Jenkins expertise and it's common on the market
What do you dislike about the product?
It's horribly outdated running on kubernetes. The company does also not seem to prioritize kubernetes native tech/setup forcing workarounds when running it on that platform
What problems is the product solving and how is that benefiting you?
Time to market and centralisation
Recommendations to others considering the product:
Consider tekton If running kubernetes - the time and effort put into converting Jenkins to tekton is regained just by ease of use and speed
Good product and support
What do you like best about the product?
Some of the CloudBees Jenkins plugins provide some really useful functionality.
What do you dislike about the product?
There appears to be a few bugs here and there in the CloudBees proprietary plugins that occasionally causes crashes. I dislike the fact that I don't know what's going on under the hood when these bugs happen so I need to open a support ticket and wait instead of being able to check what went wrong myself. We periodically have agent disconnection problems too and are unable to resolve these.
What problems is the product solving and how is that benefiting you?
We're using CloudBees CI as a orchestration tool for our CI processes as well as as a tool for automating common engineering processes. We've made a lot of improvements in the way we build and deliver software since we switched from Jenkins, being able to build and ship code much faster and in a much more robust way.
Recommendations to others considering the product:
CloudBees CI offers great support and added functionality on top of the open sourced Jenkins. The pricing and lack of visibility into the proprietary components are a downside though, so be sure to review the added functionality to determine if it is worth the cost.
stable, feature-rich, scalable, extensible and yet simple CI
What do you like best about the product?
best scalable and extensible architecture
What do you dislike about the product?
licensing model can be more flexible but not a big problem compared to value that it provides
What problems is the product solving and how is that benefiting you?
continuous integration testing, works with multiple cloud providers and one stop shop for many needs
showing 371 - 380