This cheat sheet rocks! Contains all good practices that every developer should be familiar with.

With Continuous Delivery (CD), teams continuously deliver new versions of software to production by decreasing the cycle time between an idea and usable software through the automation of the entire delivery system: build, deployment, test, and release.

CD is enabled through the Deployment Pipeline, which encompasses a collection of patterns described in this Refcard.

The cheat sheet is divided in:

Configuration Management, Continuous Integration, Testing, Deployment, Scripting, Releasing, Infrastructure, Data, Incremental Development, Collaboration and Tools

————————- 

The 1 pattern that I thought of differently is

Dark Launching: Launch a new application or features when it affects the least amount of users.

I thought about the pattern “Dark Launching” as

• Deploying a feature, without releasing it (NOT visible to end user)
• Exercising all the parts of your infrastructure involved in serving that feature

I have to ping Paul M. Duvall about that…

Get the full cheat sheet here
Continuous Delivery - Patterns and Antipatterns in the Software Lifecycle
http://refcardz.dzone.com/refcardz/continuous-delivery-patterns