Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (Apr. 4 to Apr. 10). Here they are, in order of popularity:
Every now and then in the world of security, something rather serious happens and we all run around like headless chicken wondering what on earth it means. Did the NSA finally “get us”? Is SSL dead? Is the sky falling? Well it’s bad, but not for everyone and quite possibly not as bad as many are saying it is.
If you want to understand why I think CI and CD done correctly are almost the same thing, follow me down the rabbit hole.
This article, featured in DZone's upcoming 2014 Guide to Continuous Delivery (releasing April 14th), discusses the widely-discussed design practice of Continuous Delivery. But where did Continuous Delivery come from, what does it offer, and how does it work?
I'm not scared to talk about my vision of a perfect test automation in a context of a software development. My work experience gives me confidence in this question
Continuous Delivery (CD) is a software development design practice used to increase the efficiency of the software delivery process. It encourages more frequent enhancements, and these smaller, iterative changes allow for quick bug fixes with minimal risk. Ultimately, CD is about keeping things moving.