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.
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.
We have five or six client controllers, referred to as ClientMasters, each serving a different region. For instance, we set up a client controller for the Europe region, where we manage multiple scheduled jobs. With CloudBees, we handle everything end-to-end, including installation, configuration, maintenance, and pipeline execution. These pipelines deploy our applications on Kubernetes. We also manage user access within CloudBees, using RBAC to define roles and responsibilities. Admins can access the operation center and all client controllers, while project-specific users only access their designated controllers. This setup ensures a structured and secure management of CloudBees resources.
I worked on the DevOps team and was responsible for automating build and deployment processes. My focus was on the automation side using CloudBees. Our CloudBees Jenkins instance was used globally by around 8,000 developers. We created numerous templates because CloudBees offers additional benefits over the open-source Jenkins. One key advantage was the enterprise support from CloudBees, which was extremely helpful. Whenever we performed upgrades or needed assistance, we had support from the CloudBees team, which was valuable for leveraging the features CloudBees provides, such as template creation. We developed templates for various build types, including Python, PyPI, NPM, and Maven. Developers used these templates for their builds and application onboarding. Our CloudBees instance had a high-availability architecture integrated with security tools like SonarQube and Checkmarx. Additionally, our builds were containerized and managed on OpenShift, which helped streamline agent management and regular cleanups.
We had a couple of projects we were working on. Much of it has to do with the combination of a recently acquired brand over at our parent company, and we were considering consolidating our cloud platform and our domain. We were also looking at moving applications from one team to another so that we could leverage them. We also want to increase our production automation. That may have been the most leveraged part of that. There were a lot of teams, and they were doing a lot of work. It was causing levels of concern, confusion, risk, oversight, and over-expenditure. We were looking at various applications, and CloudBees was selected so that we could consolidate and combine all of our efforts. We wanted to reduce the number of tools we were using to help deliver and standardize a lot of our processes and procedures.
In general, as a DevOps user, I mostly build pipelines and deploy them. That is mostly used for deployment and release for our products and services. But with my profession, I'm more towards taking care of the service. I take care of the CloudBees service, which is used by teams to build and deploy their releases for production services. We also use it for our own purpose, for our own build and releases. So you can say that I use it as a service and also as an admin who takes care of the service. So, on both sides.
We are running over 200 applications in CloudBees. We integrate different DevOps tools like Vault, SonarQube, Nexus, Nexus IQ, and Ansible with CloudBees. We use the tool to create multiple pipelines, like multi-branch pipelines, declarative pipelines, standalone pipelines, and parameterized pipelines. We upgrade CloudBees on a time-to-time basis. We create the Docker images and push them to Harbor using CloudBees. We also create nodes like the Ansible and Docker nodes to run the images on that particular node. For the dot net application, we configured the Windows slave machine on CloudBees.
CloudBees provides a highly scalable and secure platform that supports seamless integration and automation across multiple environments. It excels in managing Jenkins instances and offers flexible deployment options, enhancing efficiency for large teams.CloudBees is recognized for its integration with Jenkins, SonarQube, and Ansible, allowing companies to leverage its robust automation capabilities for continuous integration and deployment. With its strong support for Docker and Kubernetes,...
We use CloudBees for deploying the code in higher environments, such as QA, C2, staging, and production.
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.
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.
We have five or six client controllers, referred to as ClientMasters, each serving a different region. For instance, we set up a client controller for the Europe region, where we manage multiple scheduled jobs. With CloudBees, we handle everything end-to-end, including installation, configuration, maintenance, and pipeline execution. These pipelines deploy our applications on Kubernetes. We also manage user access within CloudBees, using RBAC to define roles and responsibilities. Admins can access the operation center and all client controllers, while project-specific users only access their designated controllers. This setup ensures a structured and secure management of CloudBees resources.
I worked on the DevOps team and was responsible for automating build and deployment processes. My focus was on the automation side using CloudBees. Our CloudBees Jenkins instance was used globally by around 8,000 developers. We created numerous templates because CloudBees offers additional benefits over the open-source Jenkins. One key advantage was the enterprise support from CloudBees, which was extremely helpful. Whenever we performed upgrades or needed assistance, we had support from the CloudBees team, which was valuable for leveraging the features CloudBees provides, such as template creation. We developed templates for various build types, including Python, PyPI, NPM, and Maven. Developers used these templates for their builds and application onboarding. Our CloudBees instance had a high-availability architecture integrated with security tools like SonarQube and Checkmarx. Additionally, our builds were containerized and managed on OpenShift, which helped streamline agent management and regular cleanups.
We had a couple of projects we were working on. Much of it has to do with the combination of a recently acquired brand over at our parent company, and we were considering consolidating our cloud platform and our domain. We were also looking at moving applications from one team to another so that we could leverage them. We also want to increase our production automation. That may have been the most leveraged part of that. There were a lot of teams, and they were doing a lot of work. It was causing levels of concern, confusion, risk, oversight, and over-expenditure. We were looking at various applications, and CloudBees was selected so that we could consolidate and combine all of our efforts. We wanted to reduce the number of tools we were using to help deliver and standardize a lot of our processes and procedures.
In general, as a DevOps user, I mostly build pipelines and deploy them. That is mostly used for deployment and release for our products and services. But with my profession, I'm more towards taking care of the service. I take care of the CloudBees service, which is used by teams to build and deploy their releases for production services. We also use it for our own purpose, for our own build and releases. So you can say that I use it as a service and also as an admin who takes care of the service. So, on both sides.
We are running over 200 applications in CloudBees. We integrate different DevOps tools like Vault, SonarQube, Nexus, Nexus IQ, and Ansible with CloudBees. We use the tool to create multiple pipelines, like multi-branch pipelines, declarative pipelines, standalone pipelines, and parameterized pipelines. We upgrade CloudBees on a time-to-time basis. We create the Docker images and push them to Harbor using CloudBees. We also create nodes like the Ansible and Docker nodes to run the images on that particular node. For the dot net application, we configured the Windows slave machine on CloudBees.