I worked for a company where we had pipelines to deploy new code and make changes in the existing infrastructure on GoCD. Another team maintains it. I was a user who used the solution to create and use the pipelines.
We are currently utilizing it for the integration aspect, specifically for the deployment phase of our project. To elaborate, we have a considerable number of Amazon EC2 instances, exceeding one hundred, and various code applications that interconnect with each other. For the deployment process, we rely on GoCD as our backend, and for the depositors, we utilize GoCD. Consequently, it forms an integrated set of GoCD. Due to the fact that the code is written in core PHP, we have opted to use GOCD.
Solution Architect | Head of BizDev at Greg Solutions
Real User
2020-11-27T13:00:00Z
Nov 27, 2020
We are using GoCD as our main tool for Continuous Delivery (CD) pipelines. We integrated GoCD with Continuous Delivery tools, such as Jenkins, TeamCity, etc. We actively using the following features of the GoCD: LDAP integration, server-agents architecture (run GoCD agents on-demand in a Kubernetes cluster or on AWS EC2 instances to keep the operations cost low), plug-in architectures, Infrastructure as a code (pipelines in GoCD could be described in code repository). Besides all these features, GoCD has a great UI with flexible permissions management.
Find out what your peers are saying about Thoughtworks, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: February 2025.
Application Lifecycle Management (ALM) Suites streamline the software development process by integrating project management, development, and quality assurance tools in a single platform.Many organizations leverage ALM Suites to ensure a consistent and efficient development cycle from conception to deployment. These suites offer comprehensive solutions for tracking requirements, code changes, testing processes, and team collaboration. By providing real-time analytics and reporting, they...
The solution helps us deploy microservices across multiple environments.
I worked for a company where we had pipelines to deploy new code and make changes in the existing infrastructure on GoCD. Another team maintains it. I was a user who used the solution to create and use the pipelines.
We use GoCD for the production environment and delivery needs, including Kubernetes container delivery.
We are currently utilizing it for the integration aspect, specifically for the deployment phase of our project. To elaborate, we have a considerable number of Amazon EC2 instances, exceeding one hundred, and various code applications that interconnect with each other. For the deployment process, we rely on GoCD as our backend, and for the depositors, we utilize GoCD. Consequently, it forms an integrated set of GoCD. Due to the fact that the code is written in core PHP, we have opted to use GOCD.
We are using GoCD as our main tool for Continuous Delivery (CD) pipelines. We integrated GoCD with Continuous Delivery tools, such as Jenkins, TeamCity, etc. We actively using the following features of the GoCD: LDAP integration, server-agents architecture (run GoCD agents on-demand in a Kubernetes cluster or on AWS EC2 instances to keep the operations cost low), plug-in architectures, Infrastructure as a code (pipelines in GoCD could be described in code repository). Besides all these features, GoCD has a great UI with flexible permissions management.