We integrate the solution with Git, where we store our code. We use Maven to build the code and tools like SonarQube and Checkmarx for code quality checks. We deploy our services in a Kubernetes-based infrastructure using Helm Charts, and all the Helm and Docker commands are executed through GoCD. It requires creating templates that can be reused in jobs. Most of the time, people prefer to use these templates, although creating jobs freestyle is possible. This differs somewhat from Jenkins, where job creation types are more defined. I rate it a seven out of ten.
The product is a bit outdated. Many modern tools like Jenkins and GitLab can replace GoCD. We have integrated the tool with GitHub for the repository and to get the pipelines working. The product is easy to use. If we have some basic knowledge about configuration management, it's a bit easy to understand the script. However, many other tools have the latest updates and enhancements. Overall, I rate the solution a six out of ten.
We spread the solution's maintenance to a team of five people and are covering more than 1500 users internally. It was easy to learn and equally easy to reach developers, which was a pleasant surprise considering it's an open-source product. We could directly engage with developers, resembling having exclusive rights or a specialized contract. When posting an issue or seeking more information, they were highly responsive and eager to provide solutions, demonstrating a proactive and helpful approach. Overall, I rate the solution a nine out of ten.
Initially, the primary consideration is the nature of the application software being used. The crucial question is whether the application software requires continuous integration (CI) or not. If the application software does not necessitate CI, then GoCD alone can suffice for managing deployments. If your project does not require any integration or deployment complexities, specifically for code written in PHP, then GoCD would be the most suitable choice. I rate GoCD an eight out of ten.
Find out what your peers are saying about Thoughtworks, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: November 2024.
Application Lifecycle Management (ALM) is a systematic approach to managing the development and delivery of software applications. It encompasses all aspects of the software development process, from requirements gathering to deployment and maintenance.
We integrate the solution with Git, where we store our code. We use Maven to build the code and tools like SonarQube and Checkmarx for code quality checks. We deploy our services in a Kubernetes-based infrastructure using Helm Charts, and all the Helm and Docker commands are executed through GoCD. It requires creating templates that can be reused in jobs. Most of the time, people prefer to use these templates, although creating jobs freestyle is possible. This differs somewhat from Jenkins, where job creation types are more defined. I rate it a seven out of ten.
The product is a bit outdated. Many modern tools like Jenkins and GitLab can replace GoCD. We have integrated the tool with GitHub for the repository and to get the pipelines working. The product is easy to use. If we have some basic knowledge about configuration management, it's a bit easy to understand the script. However, many other tools have the latest updates and enhancements. Overall, I rate the solution a six out of ten.
We spread the solution's maintenance to a team of five people and are covering more than 1500 users internally. It was easy to learn and equally easy to reach developers, which was a pleasant surprise considering it's an open-source product. We could directly engage with developers, resembling having exclusive rights or a specialized contract. When posting an issue or seeking more information, they were highly responsive and eager to provide solutions, demonstrating a proactive and helpful approach. Overall, I rate the solution a nine out of ten.
Initially, the primary consideration is the nature of the application software being used. The crucial question is whether the application software requires continuous integration (CI) or not. If the application software does not necessitate CI, then GoCD alone can suffice for managing deployments. If your project does not require any integration or deployment complexities, specifically for code written in PHP, then GoCD would be the most suitable choice. I rate GoCD an eight out of ten.