The debate of Jenkins vs Spinnaker as a Continuous Delivery (CD) tool has been making rounds for quite some time. Many are happy to use them together since Spinnaker has a native Jenkins API to delegate compilation and packaging, but once Jenkins 2.0 was released with an added focus on CD, it became fuzzy how Spinnaker really measured up. So here's a breakdown for you.
Continuous Delivery (CD) is one of those things that tend to prove beneficial for all parties. For developers, it allows them to push new code without fear. For the end user (your customer), they get exactly what they want: better features, faster updates, and the confidence that you actually listen to their feedback. Everybody wins, right?
Archana Sankaranarayanan is a senior UI Engineer at Netflix where she builds tools to improve development velocity and obsesses over creating simple, intuitive, and accessible interfaces. Before settling into her enviable position at Netflix, she lent her expertise on style guides to build interfaces for Coursera, Quantifind, and Adobe.
Kubernetes (K8s) is the go-to-guy when you’re looking to take your container game to the next level. But while K8s has certainly changed how we run cloud-native applications, it’s not a deployment tool.
If you’re in the business of building and delivering software-services then you’ve probably already entertained the idea of Continuous Delivery (CD).