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.
One of the Best Product
What do you like best about the product?
This is one of the greatest product in the industry. I love their idea totally. I love if they continue to add more plugins to integrate with upcoming tools in the market. We are using Jenkins in different environments. We recommend this product to make a use of their options available. Because Jenkin can
What do you dislike about the product?
Nothing much, as far I can see they are continue to develop everyday.
What problems is the product solving and how is that benefiting you?
All of our development teams using Jenkins. We are solving our micro service application integration issues.
Recommendations to others considering the product:
No other products can catch some of the ideas that available in Jenkins.
- Leave a Comment |
- Mark review as helpful
Cloudbees Jenkins CI
What do you like best about the product?
Ability to Integrate with most of the 3rd part tools. Easily accessible UI and great and quick support.
What do you dislike about the product?
Community driven plugins where we have minimal support. It would be good if cloudbees can provide own plugins with good support.
What problems is the product solving and how is that benefiting you?
Improved efficiency of build and test automation. Saved time and resources with distributed parallel and sequential builds.
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
Senior Devops Engineer.
What do you like best about the product?
Prompt support.
Stable tool.
Frequent updates
Stable tool.
Frequent updates
What do you dislike about the product?
Little difficult to manage , learn for new
What problems is the product solving and how is that benefiting you?
Stable enterprise environment.
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!
CloudBees CI is the must go if you're looking for CI-CD
What do you like best about the product?
Ease of use and management. It's relatively easy to integrate with a lot of tools and has a plethora of supported plugins. Multibranch pipelines are highly efficient.
What do you dislike about the product?
This is more of a recommendation, It would be great to force the controllers (formerly Managed masters) to instantiate on specific nodes. Also, the GUI is a bit outdated, it could use some re-design.
What problems is the product solving and how is that benefiting you?
Multiple teams working on several projects use CloudBees CI day-to-day to trigger jobs using multibranch pipelines. Pipelines provide a simple way to design the flow of jobs from building code to testing and promoting to various environments. They are a portable solution without having to go through the pain of re-designing the code flow during any contingency.
Management of multiple teams and abstraction of work is easy through using multiple controllers (formerly masters) . Deployment on Kubernetes cluster makes maintenance a breeze.
Management of multiple teams and abstraction of work is easy through using multiple controllers (formerly masters) . Deployment on Kubernetes cluster makes maintenance a breeze.
Cloudbees is good.
What do you like best about the product?
Their support system is good, but it really only is needed if you have people who are not technical or have not used Jenkins before.
What do you dislike about the product?
Subscription is expensive. very expensive for what you get.
What problems is the product solving and how is that benefiting you?
We are using CI for the build space. So its building our applications.
Recommendations to others considering the product:
The biggest question: do you really need cloudbees support or can you go open source? Support is helpful for those that dont have a large technical staff or the knowledge, but in our case, we have almost 500 developers and feel like we are not getting the value from the cost of the subscription.
CloudBees CD is great!!!!
What do you like best about the product?
I was/am able to easily use CI/CD methodologies without being an expert in it (at first). It was easy to pick up and automate deployments of several things in my infrastructure enviornment
What do you dislike about the product?
If I am nitpicking, the integration with K8s
What problems is the product solving and how is that benefiting you?
Automation for template patching, Docker Image updating, Infrastructure server CLUSTER rebooting all without humans
Recommendations to others considering the product:
Have the items you want to automate well defined
Have a good skillset with programming/development techniques
Have a good skillset with programming/development techniques
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
showing 341 - 350