There was a quote (pg 9) that rang true to me related to process subversion that was an antipattern. This is something that requires a cultural shift to overcome.
As pressure increases the defined process for collaboration between the development and deployment teams is subverted in order to get the deployment done within the time allocated to the deployment team
There is very little visibility into our testing env (deployment-prep) for anyone
We use Puppet to enforce existing state and tweak existing systems rather than provision from scratch
Without CI, your application is broken until you prove otherwise. With CI, the default state of your application is working, albeit with a level of confidence that depnds upon the extent of your automated test coverge
The "short build" section is much less than we currently have
"commit" stage is "test"
"acceptance" stage is "gate-and-submit"
some portion of "gate-and-submit" should likely become post-merge
The problem with post-merge tests is how to fix them
this is part of the cultural shift
we haven't checked in with folks about this kind of thing...ever (as long as I've been around)