CloudBees Jenkins Enterprise
CloudBees | 2.73.2.1Linux/Unix, Ubuntu 16.04 LTS - 64-bit Amazon Machine Image (AMI)
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.
Good CI Tool
What do you like best about the product?
Customizable and lot of plugins and great team support
What do you dislike about the product?
Getting a new feature and some time support was little slow
What problems is the product solving and how is that benefiting you?
We are achieving End to End to CI. It help
us save lot of money and time
us save lot of money and time
- Leave a Comment |
- Mark review as helpful
Automation carried out correctly
What do you like best about the product?
I appreciate that CloudBees CI provides a large number of integration mechanisms with other products such as Jenkins, which we use heavily in our cross-team communication and collaboration.
Over time, the quality of the contracted service has been poured into the final product that we offer to the ultimate consumers, and the results have been nothing short of spectacular.
Over time, the quality of the contracted service has been poured into the final product that we offer to the ultimate consumers, and the results have been nothing short of spectacular.
What do you dislike about the product?
There are fewer minor hitches in the latest version of their product than in previous versions. Specifically, the workflow functionality, which is supposed to spin up multiple concurrent Docker images for text execution, does not reliably feed back the results statistics.
What problems is the product solving and how is that benefiting you?
Our IT and cyber-security solution is developed using the Salesforce platform, which is used by our organization. We have a high level of unit test coverage, which Salesforce requires in order for us to be allowed to advertise our application in their App store. For the management of our software development process, we required a dependable continuous integration and delivery system. We used Atlassian Bamboo for a number of years before making the switch to CloudBees CB to provide cloud integration. This is used for testing purposes.
Recommendations to others considering the product:
CloudBees is essential for any professional software development company that is concerned with ensuring that their code is adequately test covered. The software provides a very easy configuration procedure with the use of CB. Jenkins and is easily adaptable to meet the needs of any type of development project.
CloudBees CI is a fantastic organization.
What do you like best about the product?
This software contains a robust community forum as well as RRSS. When I encountered a bug and was able to remedy it with the help of the community, I wanted a place where we could all share details and short information.
What do you dislike about the product?
Running local builds for the purpose of diagnosing issues might be time-consuming. The Docker image that I recall was very much a black box, and it was difficult to figure out why I was getting the results that I was. However, this was to be expected. Otherwise, it would be straightforward for other suppliers to replicate their features if the system was not a black box.
Initially, some aspects of the cache configuration were a little difficult to understand.
Initially, some aspects of the cache configuration were a little difficult to understand.
What problems is the product solving and how is that benefiting you?
A SaaS application's front-end and back-end components are being continuously integrated utilizing CB, which we're employing to do this. Due to the fact that it is linked to a well-known source code repository, integration is a breeze.
Recommendations to others considering the product:
CB is the best choice for those looking for a simple CI/CD solution. The latter is especially true for smaller projects that do not require a great deal of intricacy or construction time.
For small jobs, this is a highly recommended option. And will almost certainly become a paying customer if the complexity and construction time are justified.
For small jobs, this is a highly recommended option. And will almost certainly become a paying customer if the complexity and construction time are justified.
Continuous Integration Tool that works well
What do you like best about the product?
Simple to comprehend and use, the CB web interface (UI/UX) is very easy to learn and use, and Easy Configuration is very simple to learn and use. Jenkins configuration is included in a single file.
What do you dislike about the product?
The cost of the product in comparison to certain alternatives that are less expensive or free. This is especially true if you are running numerous containers in a single instance. I, too, have experienced a number of outages (3-5) where CB has been unavailable in the last few months..
What problems is the product solving and how is that benefiting you?
Continuous integration across all of our software applications and environments is made possible with the use of CB. CB enables us to create complicated workflows that include steps to run pre-deployment and post-deployment scripts, perform test suites, and send slack notifications, among other things. With CB, we can ensure that code that has been "broken" does not make its way out into the wild.
Recommendations to others considering the product:
If you, your developer, or a team of developers have already worked with it, you should feel comfortable using it. They won't have to go through the learning curve of yet another Continuous Integration solution, which saves them time and money. CB supports Continuous Integration workflows exceptionally effectively, even when the procedures are quite complicated. In light of the foregoing,
Make it easier for your engineers to generate, test, and deploy code quickly
What do you like best about the product?
Builds that are automated This is the primary reason for acquiring Cb: to automate the construction process. As a result, the process of developing your application becomes significantly more predictable and repeatable. It can also do tests to ensure that your application is functioning as planned.
What do you dislike about the product?
The search function might use some tweaking. If you're conducting a lot of builds, the history can take up several pages of your computer's hard drive. We didn't find it to be a good fit for our auditing/reporting requirements because you can't search for a specific developer who initiated a build, or filter for only successful builds, among other things.
What problems is the product solving and how is that benefiting you?
Because our SaaS platform has transitioned to a continuous integration/continuous delivery paradigm, the tool Cb is essential in automating the creation, testing, and deployment of all non-production environments. Whenever a developer needs to test something, they may trigger a build, which will either recycle a previous development environment or launch a new development environment that will not interfere with any other builds in the pipeline.
Recommendations to others considering the product:
Cb is ideal for use in a CI/CD pipeline for an application that follows a conventional build process. It will require more effort to manage a sophisticated build process, but it should be sufficient for most tasks unless you want extensive integrations with other tools. If you have a large team and can spare someone who can devote their entire time to simply the CI/CD tools, do so.
Continuous integration and pipeline for software development.
What do you like best about the product?
As far as test driven development (TDD) goes, I believe this is one of the best options because of its speed and fluidity when compared to other tools like circleCI.
What do you dislike about the product?
Only one thing from time to time when integrating and developing functions that is the scope of view.
What problems is the product solving and how is that benefiting you?
My team uses CB CI as a continuous integration and deployment pipeline for code and other programmatic work. Deploying, testing, and producing code for our main software engineering functions are some of the business issues it addresses Other teams we work with follow the same path and use similar tools, such as cycles.
Recommendations to others considering the product:
is a great option if you need to drastically scale and test your software engineering processes before deployment. It works with standard code structures where a procedural lifecycle is present and methodical execution is required.
One of the few with kubernets integration
What do you like best about the product?
We found just the right software for our local team administrations. What I like most about CloudBees CI is that its modern cloud platform is designed to run on Kubernetes, which is hard to find.
What do you dislike about the product?
Extremely slow support team, we have spent many weeks trying to solve a problem for which we still do not have a definite solution and we need an answer.
What problems is the product solving and how is that benefiting you?
We mainly use it as an integration for the installation of apps and the development of web models, the CI/CD, Test automations allow us to advance and give us a broad view of the panorama among other private functions.
Recommendations to others considering the product:
The Testautomations CI/CD lack load and space for large files and I think this is a fucking essential to improve.
Highly recommended for engineers integrating
What do you like best about the product?
That program saves us a lot of time and money every time we use it in our integrations, and that's what I'm responsible for as an engineer because of the consistency with which it works.
Full-featured, cloud-native CloudBees CI, which can be hosted on-premise or in the public cloud, is used to deliver CI at scale in this sense of scale, which helps us achieve our personal and business objectives.
Full-featured, cloud-native CloudBees CI, which can be hosted on-premise or in the public cloud, is used to deliver CI at scale in this sense of scale, which helps us achieve our personal and business objectives.
What do you dislike about the product?
Only UX can be difficult to understand and navigate in the beginning.
What problems is the product solving and how is that benefiting you?
Chef cookbook CI/CD pipeline is being implemented. As a result of the use of CB Core, we have been able to establish a well-defined pipeline for the release of new features. On the other hand, the development of software and services that we provide come in a more expeditious way with the program.
Recommendations to others considering the product:
I believe in development completely as well as the cool and easy automation it provides. I think they should acquire it without further delay.
My CB Rating
What do you like best about the product?
We like that the Pipeline technology used is favorable for Continuous integrations. This allows us to rest assured in the future of being able to continue using the processes and not having to change with the supplier team inevitably.
What do you dislike about the product?
So far I've only been upset by a few issues with support for some technical difficulties, but I think it's an isolated occurrence. The rest of my team has not gone through the same difficulties in support.
What problems is the product solving and how is that benefiting you?
The first was the increase in space that we needed for apps and other smooth updates, to have a work program that would align future ideas to provide better services. It has to do intrinsically related to Drive innovation,
Drive revenue growth, Improve business process agility points that we need to take care of.
Drive revenue growth, Improve business process agility points that we need to take care of.
Recommendations to others considering the product:
I recommend that they try to check if the support is what suits them in terms of efficiency and speed, since in this technology sector, being so competitive, customers can be lost due to the lack of timely help in solving a problem that has to do with with the service or product to a customer.
My good Experience with CloudBee CI
What do you like best about the product?
Cloudbees CI's best feature is role-based access control. From the folder level down to the specific Jenkins jobs, we have the ability to separate.
What do you dislike about the product?
Because there are a lot of unanswered questions on the forum and online.
What problems is the product solving and how is that benefiting you?
-Improve efficiency within the company's operations.
-Improve the agility of business processes
-Management of the cost of goods and services
-Make it easier for new products to reach consumers
-Improve the agility of business processes
-Management of the cost of goods and services
-Make it easier for new products to reach consumers
Recommendations to others considering the product:
Consider pre-tested features like this before you buy, try trying open source Jenkins in-house first, then realize how difficult it is to manage access. In this way you will consider acquiring CI.
showing 111 - 120