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.
CloudBees CI is to use for any sort of automation for build and deployments
What do you like best about the product?
Very useful when using with multi branch pipelines. Easy to connect agents and adding separate Jenkins nodes for different products when we have more load. We can easily connect the other tools like bitbucket , Harness, artifactory and Jira to have easy automation. Blue ocean UI is very much recommended by our developers and testing team to have more visibility in the logs.
What do you dislike about the product?
Difficult UI to use while configuring the jobs. And Global config takes very long time to load.Deployments are a bit difficult to configure . Windows connectivity to Amazon AWS agents is having lot of bugs. Sometimes we experience lot of problems with number of plugins and it is difficult to identify which plugin is causing the problems.Lot of times we endup in uninstalling the plugin which are old or deprecated. Only few of them are supported by Cloudbees support.
What problems is the product solving and how is that benefiting you?
We use CloudBees CI for our daily builds and deployments. And also use CloudBees CI for self service jobs which help to increase the developer productivity. We use for our CI for almost all the products and Test Automation and also for mobile device testing.
We are also solving all the automation required for the QA teams and Dev Ops teams and also UI teams for day to day automations.
We are also solving all the automation required for the QA teams and Dev Ops teams and also UI teams for day to day automations.
Recommendations to others considering the product:
Because of pipeline support and more flexibility and easy to configure agents and adding separate Jenkins nodes for different products when we have more load.We can easily connect the other tools like bitbucket , Harness, artifactory and Jira to have easy automation. Blue ocean UI is very much recommended by our developers and testing team to have more visibility in the logs.
- Leave a Comment |
- Mark review as helpful
Good product to automate everything
What do you like best about the product?
Lots of plugin and open source version too
What do you dislike about the product?
Interface is outdated and slow sometimes
What problems is the product solving and how is that benefiting you?
We automated all our build and releases globally
Recommendations to others considering the product:
Make sure to not just add plugins you need to understand what you are doing first
It has been good but experience but not great
What do you like best about the product?
If in case we get stuck with the issues, the support is good.
What do you dislike about the product?
Want to see more integrating capabilities for signing in with Microsoft AD and other vendors.
What problems is the product solving and how is that benefiting you?
We are using Cloud bees Jenkins to do our CI/CD in the automated fashion.
Currently using cloudbees in our company for numerous CI stuff and its working great
What do you like best about the product?
The easy scalability and usage. We are deploying around 10-20microservices using it
What do you dislike about the product?
currently none. Till now we haven't faced any issue in it.
What problems is the product solving and how is that benefiting you?
We are creating docker images and sonarqube cronjobs using Cloudbees which is increasing our code quality and work
Perfect package to manage your software delivery
What do you like best about the product?
Cloudbees Jenkins and Jenkins Core. both give me an ultimate experience of having our whole organization a stop shop to place all the projects at one place and very easier to manage all of it. Also, we can leverage the configuration by project basis which is really awesome.
What do you dislike about the product?
There are few plugins which are only available in the paid version. Cloudbees should enable some of them for community edition as they play a major role for everybody using the Cloubdees products.
What problems is the product solving and how is that benefiting you?
We've solved the manual process of building, promoting to env's. Deployment to higher env's. it's all automated now with cloud bees Jenkins
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.
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
showing 371 - 380