Agile DevOps: Transient environments

See the original posting on IBM developerWorks – Java

Often, after a shared environment is provisioned, it's never
decommissioned and might run for weeks or months, with engineers applying
manual configuration changes throughout its lifetime. This risky approach
regularly causes deployment problems and other strange "environment" errors to
occur during development, test, and production cycles. This Agile DevOps
installment explains how to create ephemeral environments that are terminated
on a frequent basis. Once all environments are scripted and versioned, these
test environments are only used long enough to run through a suite of tests as
the software moves through a delivery pipeline on its way to
production.