GoCD vs. Spinnaker

GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.

Incentivized

Spinnaker is a strong solution for Continuous Deployment being able to manage enormous environments in an easy way. Even Spinnaker being able to manage environments based on cloud instances (ec2 for example) I believe it is more suitable for containerized environments. Mainly in Kubernetes where it excels as a reliable and safe tool

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

• The immutable way of deployment is one of its greatest advantages.
• We have a strict policy to restock our instances with new images very frequently and this can be done very seamlessly via Spinnaker
• Rollback/ resize of clusters is one of the coolest features of Spinnaker.

Incentivized

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

Incentivized

• Integration with external authentication mechanism is not that simple.
• Its configuration is made by a external tool (halyard). Would be better if we could configure it by using its own frontend.
• Its user interface is some times a bit confusing.

Incentivized

I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.

Incentivized

• Pipeline Expressiveness • Self-Service/Override • Visibility of Client Teams • Operability of Client Teams - • High-Quality Integrations (AWS, IHP, Google) • Extensibility – (Ability to add code) • The maturity of Deployment Process • Speed/Ease of Onboarding

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

• It's open source!
• RPM based deployments can be scripted at Maven file itself , so very easy!
• RPM based deployments bundles all code and configs together, so awesome!

Incentivized