CloudBees [Private Offer Only]

The primary use case for CloudBees  is for continuous integration and deployment. It is primarily used for production deployments. We use it to trigger Autobahn, such as CloudBees , well in advance to clear out many issues upfront, trigger change requests, and test in various environments to be ready with the production deployment on the actual date.

CloudBees has helped our organization by integrating with various systems like version one, GitHub , and PDSM. It reduces the need for documentation by automating processes, saving time when creating documents and testing the application. This reduces the amount of time spent on deployments and helps pull out all the test results and create change requests, providing a more streamlined process for deployment.

The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub , and PDSM. It automates documentation and testing processes, reducing the need to create documents manually. By creating automated processes, it saves time and effort.

It could improve the document upload process. Currently, documents need to be uploaded manually to the PDSM request. An enhancement could be to have a feature where you can upload documents directly to go into the PDSM request.

For about two to three years, approximately two and a half to three years.

CloudBees has improved a lot over time. Initially, there were challenges setting it up, but once we understood its functions and processes, there were no stability issues.

CloudBees is scalable as it integrates with various complex systems and offers the flexibility to scale to many other application integrations beyond those currently used.

I have not personally interacted with customer service or support since the DevOps team handles template creation and maintenance, and they might have contacted support during the initial phase.

Positive

Before CloudBees, we did not use a similar tool. However, we are currently considering a transition to GitHub Actions .

The initial setup involved creating a template that checks pull requests in GitHub. It verifies approvals, mergers, and other criteria necessary for a build. The setup includes extensive integration with other systems, stringent checks, and a series of deployment stages from QA to production.

The DevOps team is responsible for creating templates and handling integration with various systems. They play a crucial role in supporting the implementation and deployment processes.

The measurable benefits of using CloudBees include a significant amount of time saved during deployment because of the automation and integration capabilities it offers.

I am not aware of the pricing, setup cost, or licensing details for CloudBees.

We are currently using GitHub Actions , with an effort to transition from CloudBees to GitHub Actions.

Follow the guidelines and step-by-step processes thoroughly. If you encounter integration issues with your tools, seek support from CloudBees to ensure integration. Once set up, CloudBees is a reliable tool for deployment.

I'd rate the solution nine out of ten.

We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.

CloudBees has made deployment faster compared to on-premise solutions. It also facilitates working with multiple machines, improving efficiency and performance.

I find the automation feature most valuable. CloudBees is highly scalable and supports both small and large teams. The deployment process is also faster when compared to on-premise.

There are connection issues with CloudBees, specifically between Sybase and CloudBees. We often encounter connection problems, and there are issues with the pipelines.

I have been working with CloudBees for one and a half years.

There are a lot of connection issues with CloudBees. We experience disconnections frequently.

CloudBees supports the deployment of large amounts of data efficiently across multiple machines.

I haven't gone through the technical support, so I can't comment on it.

Positive

Before CloudBees, we were using Jenkins on-premises. We switched to CloudBees because we moved our SQL servers to the cloud, which made deployment easier.

The initial setup of CloudBees took approximately fifteen to twenty minutes.

We used UrbanCode deployment to deploy it in different environments, but I was not directly involved in the implementation part.

I am not aware of the return on investment metrics for CloudBees.

I am not sure about the pricing, setup cost, and licensing for CloudBees. The team takes care of it.

I am not aware of any other solutions that were evaluated before choosing CloudBees.

I would recommend CloudBees to others because building jobs is much easier than with other solutions.

We use a pipeline to deploy our application. All our organization checks and requirements are added to the CloudBees  pipelines, ensuring code quality and checking vulnerabilities. We use Jenkins  and SonarQube  as part of the deployment process.

CloudBees  has streamlined our deployment process. Previously, deployment involved manual file transfers and checks, which were time-consuming. Now, with CloudBees, many tasks are automated, making our work easier and more efficient.

CloudBees assists by automating tasks, previously done manually, in the pipeline setup. This saves time and improves efficiency. The features set rules that are regularly updated, reducing the need for constant oversight. One-click deployment processes also highlight the flexibility and ease of the platform.

Sometimes, there are performance issues, however, they may be due to our organization's configuration. Currently, I do not have specific improvements in mind as these might be related to our side.

Previously, our organization had an on-premise solution, but we have moved to the cloud version.

Due to security constraints within our organization, the performance can appear slow. It is difficult to discern if the issue is with CloudBees or our organization's configuration.

CloudBees is scalable, but I cannot provide specific details on how this scalability impacts us.

We experience issues with the CloudBees pipelines occasionally, like resource limits or permission errors. The DevOps team generally resolves these, and I would rate CloudBees support eight out of ten.

Positive

Before CloudBees, we used FTP for deployment, which involved no pipelines.

The setup was managed by a separate team. My experience starts with using the product, which was straightforward.

A separate team, the DevOps team, manages the CloudBees setup and any technical support needed.

CloudBees saves time and resources by executing automated deployment processes, which would otherwise have been manual and time-consuming.

I am not aware of the pricing, setup cost, or licensing details.

I have not evaluated other solutions, as my interaction began with CloudBees directly.

I would recommend CloudBees, especially to those using traditional ways of deployment, because it simplifies and automates many processes.

We use CloudBees  Jenkins  with Jenkins  and Sonar  validation for our pipeline. We use it for all microservices, web system payment integrations, and overall pipeline configurations and deployment processes.

CloudBees  has improved our DevOps practices by allowing us to deploy features and fixes efficiently. It supports our business rules, security analysis, and overall deployment process while simplifying the configuration.

The most valuable features are Java features, microservice communication, payment validation, Jenkins Sonar , management master to CloudBees, Blue Ocean, JobConfig, and support.

The user interface of CloudBees is good but could be even more intuitive. Improving the user-friendliness of the interface and having simpler setup configurations would greatly benefit new users.

I have been working with CloudBees for around two to three years.

CloudBees is very stable and reliable. From one to ten, I would rate the stability a ten.

CloudBees offers high scalability. On a scale from one to ten, I would rate its scalability a ten.

Customer service and technical support are excellent. I rate the technical support from one to ten as a ten. They provide fast, simple, and efficient support.

Positive

Before using CloudBees, we used Jenkins SonarQube, Nexus, Azure , and AWS . The decision to switch to CloudBees was made for better integration and deployment capabilities.

The initial setup of CloudBees is very easy and straightforward. It takes around 20-30 minutes to deploy completely without any complicated steps.

Our configuration team handled the setup and deployment. Twenty people were involved in the deployment and maintenance processes, and they ensured everything worked perfectly without delays.

CloudBees provides a robust and efficient solution for our DevOps needs. Ensuring an intuitive user interface and simplifying the setup process can further enhance its usability for new users.

CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization.

It has dynamic node allocation for the code we're building. When we trigger a build, like for Java code, it pulls a Docker image from a repository. Then, a pod spins up. If you have ten nodes, the solution uses a Kubernetes architecture. There's one master node and ten different nodes connected to the master. Whenever we trigger a build, a pod spins up and gets scheduled on any of the slave nodes in the Kubernetes cluster. That's the best thing I see about the product. 

The management is good. You don't need to manage different nodes individually. You don't have to specify which node to build the code on. In CloudBees, you can avoid that. You mention the node, and it will automatically schedule the pod on whichever node is free.

You can also configure different nodes. Another good point is that you can configure Elastic File System to store the data.

The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it.

I have been working with the product for three years. 

I have no issues with the tool's stability. 

I find the product scalable. Currently, we're using a Kubernetes architecture and working on-premises. However, other teams are working on the cloud version of CloudBees with AWS infrastructure. There, we can also scale the nodes.

I'm currently working for an organization that has over 200 applications. They've adopted the CloudBees architecture. So, these 200 applications have 200 different masters. All of this is managed by a single team, which is a separate team. The different applications and different members are managed by a single person who oversees the entire organization, similar to how we have it in AWS.

The tool's support is good. 

Neutral

I don't think CloudBees requires much maintenance, but some things must be considered. As I said, they have a Kubernetes architecture, so Kubernetes patching and Jenkins patching will also be required. It publishes upgraded versions on its website. You can purchase the latest license and upgrade the Jenkins version through that purchase.

I rate the overall solution an eight out of ten.