GoCD vs. OpenText Operations Bridge

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

Any customer who is looking for a unified monitoring solution with event Management and also looking for AIOPs. Good coverage of technologies coverage, however if any customer looking for better dashboarding solution then it may not fit. thou MF got BVD but it seems like more complex

• 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

• The software includes several user-friendly features, such as a customized dashboard, drag-and-drop event management, and an integrated knowledge base.
• If you are considering purchasing a product, keep Micro Focus Operations Bridge in mind before making a purchasing decision.
• In addition, the purpose of the product is comprehensive, which means it will benefit your business in many ways.

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

Incentivized

• Overall dashboards can be better
• Agent onboarding can be more automated than manual

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

• 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

• Monitoring, OOB plugins, Event Management and AIOps are good
• Dashboard and agent onboarding could be improved as one of our customer was not happy with the same