GoCD vs. OpenText SiteScope

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

SiteScope is definitely well suited in an HP server environment. It is also well suited for virtual server environments. It is also well suited for those who are happy with email and text based message alerting. It may not be appropriate in other environments where monitoring physical components is critical. Because HP SiteScope does not monitor certain physical components, it does fall short of being able to be a "one stop shop solution" in regard to monitoring. It is not well suited for those looking for logic in how alerts are sent and cascade to other people or groups.

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

• Alerts can be configured as per business requirement.
• It can take remedial action, when defined for a particular situation.
• Severity, priority of tickets which are created upon a trigger can be well defined.
• The teams which need to be alerted can be configured in the tool itself, in case of any event.

Incentivized

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

Incentivized

• Sitescope is particularly used for infrastructure monitoring. Other kinds of monitors cannot be set using HP sitescope.
• Sitescope cannot have graphs like splunk which is why we have splunk as well which is an additional cost for the company.
• We can't have a direct regex operations on data inside HP sitescope. We need to have the logs placed as a single log and then do that.

Incentivized

Very straightforward and easy to use once you get past the short learning curve.

Incentivized

Can't really answer this. Setup was easy and no support has really been used at this point.

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

SiteScope unified console is a powerful tool for operators to easily detect warnings and alerts grouped by its hierarchical organization with real-time status displaying continuously the whole health map.

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

• Sitescope does exactly what it was purchased for. It may take some time to set it up but once its set up it is a rock solid product.

Incentivized