Continuous delivery

This is a very good post that goes beyond the "party line" and actually talks about the pros and cons of CD: http://agile.dzone.com/articles/continuous-delivery-vs

Update: good complement to this article: http://www.infoq.com/articles/test-automation-continuous-delivery

Neo4J and CMDB

Interesting insights on Neo4J but more so regarding what he is trying to accomplish as a CMDB: http://java.dzone.com/articles/why-i%E2%80%99m-pretty-excited-about

Continuous delivery Pattern

This is a must read article: http://www.infoq.com/articles/Continous-Delivery-Patterns

Good post on Continuous Delivery

There is a good post on Continuous Delivery that can be found here.

 The point in continuous delivery practice, is that it enforces the development team, the QA team and the Managers, to invest heavily in automation. If each code change, is a potential production version, to keep up the speed, you have to automate everything. There is no time for manual regression testing, there is no time to write deployment manuals and there is no time to execute any of the steps needed to promote a software change to production, manually.

What I like about this post is that in a few line you know if CD is for you or not. It's definitely in our near future at Crowd Advisory

Continuous Integration -->Continuous Deployment...

 http://searchsoftwarequality.techtarget.com/feature/Continuous-integration-Tools-and-trends

But, according to Paul Duvall, author of Continuous Integration: Improving Software Quality and Reducing Risk,continuous deployment can go a step further. “Simply said, continuous deployment implies that you’re deploying your software to some environment, but it doesn’t mean that you’re delivering software to users,” he explains. “Delivering software to users on a frequent basis is what continuous delivery is all about. Continuous deployment could be continually delivering software to just your testing environments. This is excellent, but you haven’t necessarily gotten it to production yet. Continuous delivery implies continuous deployment, while continuous deployment does not imply continuous delivery.”

CI and code quality

Quick read, yet relevant: DevOp Zone

The purpose of this blog entry was to make explicit that little implied condition in CI -- that the integration must not decrease the quality of the code base. We've demonstrated how this condition can be used to derive the typical implementation of CI (the build and test loop) and Continuous Delivery.