GoCD vs. ManageEngine Site24x7

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

[Site24x7 All-in-One Monitoring is] well suited in website monitoring where especially for uptime and availability of the website. Due to its cloud nature, the company has servers distributed globally that allow to check site availability from anywhere in the world.

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

• Very clean website UI. Tests are well categorized and navigation is very simple.
• The accompanying mobile app is very useful when on the go as it can also notify you of any issues.
• The cost of the platform is very cheap and the cost also scales at a low amount.
• No on-premise footprint. All cloud-based.

Incentivized

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

Incentivized

• Ability to edit an existing maintenance schedule, vs creating a new one each time
• Grouping of emails to SMS and non SMS alerts to save on false alerts
• Setup of Realtime user monitor was not as functional as expected with regard to adding 3rd party scripts.

Incentivized

I have only had to use support once, so I can't go into much detail about their support team. The one time I did use it the response was fast but the resolution took some time.

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

The biggest difference between Site24x7 and products like PRTG, Nagios, or Icinga, is that Site24x7 is hosted off the network, completely externally. The others do a great job on network alerts-- and some can even be configured to send SMS or phone calls with the right equipment and plugins-- but they usually reside in the network or at least on-site. Hosting them in the cloud might be a way around that, in which case they would be pretty similar to Site24x7 in capability, but without the additional software costs in the case of Nagios and Icinga (both open source).

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

• Cost savings have been substantial at approximately 70%.
• We do suffer delayed email notifications and regular locational failures from 24x7. However, this is easily overcome by extra locational checks.
• Much quicker responses from out of hours teams with the benefit of the mobile app, which is user-friendly.

Incentivized