GoCD vs. Micro Focus Diagnostics (discontinued)

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

I would say on 90% of our agent installs everything works without any modification. If the application however makes a large use of memory based cache and analysis that classes will need to be excluded from instrumentation or it will impact performance.

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

• Agent level customization - For highly performant applications we can easily exclude instrumentation, yet still receive the benefit of historical tracking on common data points like CPU, Heap and GC cycles.
• Support - In the 5+ years working with the product any HP solution engagements have been quick to provide a needed configuration solution.
• Agent Diversity - Have used the product across 6+ differing middleware technologies comprising dozens of version (both middleware and java) combinations.
• Agent installation - With its ability to support a silent type install, automating was a simple task.

Incentivized

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

Incentivized

• The product does offer a lot of functionality - This can lead to a cluttered user interface and does take some time to become comfortable and proficient in its use.
• Data Volume - We have had some issues in balancing the desire to keep all data and consuming infrastructure storage.

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

While it has been several years since using BMC Patrol I like that HP doesn't require me to have a custom module added for every different type of product I would like to instrument.

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

• Performance Tuning - Product is fully integrated to provide baseline and drift across releases.

Incentivized