GoCD vs. KACE Systems Deployment Appliance (SDA)

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

It is most effective in Windows PC environments and doing mass Windows deployments across a wired LAN. It would not be suitable for small office/school environments or for environments with limited PC usage.

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

• Windows PC deployments.
• Windows PC re-imaging.

Incentivized

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

Incentivized

• USMT had issues with successfully capturing user states.
• MAC support, stopped supporting newer versions of MAC OS. No APFS support.

Incentivized

The majority of the support reps I talk to on the phone are quick to respond and very helpful. They will take their time helping you with any case for the SDA and have any issues with it. They will help you build new boot environments or deployments if you get stuck or have a problem.

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

• 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

• Primarily saves us time for maintaining our computer labs.

Incentivized