Spinnaker Is (Still) Not a Build Server: Debunking 8 Common Myths about Spinnaker
Oct 31, 2019 by Stu Posluns
Spinnaker is a thriving open source project backed by, and used by, some of the biggest, most technically advanced companies in the world. However, there are some misconceptions about what Spinnaker can and cannot do, where it is in the open source software lifecycle, and how difficult it is to use. These myths are surprisingly sticky… but we at Armory are here to debunk them. We’ve published a free ebook tackling eight of the most pervasive myths about Spinnaker’s strengths, weaknesses, and adoption that we’ve encountered. Think of it as the DevOps version of Mythbusters.
The myths we bust include:
- Jenkins (or Helm or AWS CodeDeploy) work just as well
- Spinnaker is a build server
- “Our team can develop a better solution internally”
- Spinnaker is a dead project that people don’t use
- Spinnaker is not production-ready
- Spinnaker only does Kubernetes
- Spinnaker can’t run on-prem
- Spinnaker is too hard
Armory is committed to ensuring the continued growth and success of Spinnaker as a core part of our mission to help teams ship better software, faster. Download the ebook to learn more about Spinnaker, and reach out to us to talk about how Spinnaker can bring velocity, clarity, and consistency to your code deployments. We’d love to chat!
