Architecting Continuous Delivery

Last month I participated in my last Electric Cloud #C9D9 Panel discussion for the year and it was definitely a great experience.  Don’t get me wrong, the other two panel discussions I was on (Version Control & Continuous Deliveryl & Test Driven Development) were great, but this episode talked about the areas that can tend to be overlooked when building a continuous delivery pipeline.

My only regret with this episode is that it should have been a two hour special.  The overabundance of information provided by the panelists was insightful.  I recommend watching the episode in its entirety, but here’s what I took away from it.

• An application designed with “independent” components will make code management and release management easy.  However, it will require a bit of work to get the right testing strategy in place.
• Define your pipeline and the environments (infrastructure, deployment scripts) you will need to support your process.
• Test data needs to be carefully thought out for each environment the application is being tested on.  Develop the scripts early and automate your tests to be data independent.

Checkout the full episode or visit Electric Cloud to learn how their solutions can help to release software faster.