Spinnaker is an open source continuous delivery platform with a range of cluster management and deployment management features, originally developed at Netflix.
Even Jenkins being originally a Continuous Integration solution, I've used it as a Continuous Deployment solution as well, but Spinnaker brought to me a more focused approach allowing us to spend less time by creating and managing pipelines. While on Jenkins we need to install …
We get a centralised view of all pipelines in single place. This helps for a large enterprise. Maven is very popular, so generating RPM from existing POM.xml is cool!
Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
• 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