Jenkins is overtaking the product. The product must enhance user experience. Jenkins has everything in a simple XML format. However, GoCD is complex. Upgrading it to a simpler language would be helpful. The tool must be more user-friendly.
GoCD could cover the authentication aspect. Currently, we are handling an in-house development that needs this. Comprehensive features must be established before transitioning into an enterprise product.
The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us. I would prefer to streamline the user management process, which would be more convenient for me. It would involve importing users from GitLab and granting them the necessary permissions they require.
* If the workflows were updated for any reason, such as when environments are created, deleted, or changed, the previous delivery pipelines will be broken. You can't redeploy the old version or propagate new versions to the following environments. * It would be great to have more flexibility in configuring the initial job. We are using GoCD for the CD process only, so any jobs are triggered by external CI tools, not the GoCD itself. We don't need to configure code repositories or other inputs that GoCD is expecting, so we are forced to create the dummy repository, and the commit history is not relevant to the CD process. * It would be great to have more available plug-ins to cover more functionality inside GoCD. * The documentation really should be improved by including real examples and more setup cases.
Find out what your peers are saying about Thoughtworks, Microsoft, Atlassian and others in Application Lifecycle Management (ALM) Suites. Updated: March 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.
Jenkins is overtaking the product. The product must enhance user experience. Jenkins has everything in a simple XML format. However, GoCD is complex. Upgrading it to a simpler language would be helpful. The tool must be more user-friendly.
GoCD could cover the authentication aspect. Currently, we are handling an in-house development that needs this. Comprehensive features must be established before transitioning into an enterprise product.
The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us. I would prefer to streamline the user management process, which would be more convenient for me. It would involve importing users from GitLab and granting them the necessary permissions they require.
* If the workflows were updated for any reason, such as when environments are created, deleted, or changed, the previous delivery pipelines will be broken. You can't redeploy the old version or propagate new versions to the following environments. * It would be great to have more flexibility in configuring the initial job. We are using GoCD for the CD process only, so any jobs are triggered by external CI tools, not the GoCD itself. We don't need to configure code repositories or other inputs that GoCD is expecting, so we are forced to create the dummy repository, and the commit history is not relevant to the CD process. * It would be great to have more available plug-ins to cover more functionality inside GoCD. * The documentation really should be improved by including real examples and more setup cases.