GoCD vs. OpenText Dimensions RM

Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.

Incentivized

from my point of view its usually suited for a project with 20 to 50 members in it. have more than that may cause issue. because of sharing will be difficult among more people

Incentivized

• Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
• The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
• Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.

Incentivized

• Traceability - will allow you to see end to end how requirements are related to each other, to project artifacts, how the requirement was tested, and the implementation code (when using with Serena CM).
• Baselines - these are snapshots in time which are typically used at project phases and milestones. They allow you to see all aspects of a project from requirements to testing and how it has progressed or changed over time.
• Test Management - test steps, execution, defect management are all included in RM, providing a powerful SDLC management platform.

Incentivized

• UI can be improved
• Location for settings can be re-arranged
• API for setting up pipeline

Incentivized

• it is a centralized software so the issue is only one user can have access to software at a given point of time
• some times check-in and check out takes time
• its little difficult for newbies to understand and work with

Incentivized

GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.

Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.

Incentivized

Incentivized

• ROI has been good since it's open source
• Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
• More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date

Incentivized

• management of requirement is much easier
• centralized access to all the document
• better user friendly experience

Incentivized