DevOps has successfully conquered many IT departments and brought a new era of collaboration. With DevOps developers gain more control over the production environment and can do more on their own. Admins learn to code their infrastruture and to build delivery chains.
But what about the risk of allowing more people to bring changes into production? Advanced automation can also quickly propagate human error to all the platform. How to trust everybody with production level access?
Common wisdom has it that test efforts should be related to the risk of a change. However, the reality is different: Developers build elaborate automated test chains to test every single commit of their application. Admins regularly “test” changes on the live platform in production. But which change carries a higher risk of taking the live platform down?
What about the software that runs at the “lower levels” of your platform, e.g. systems automation, provisioning, proxy configuration, mail server configuration, database systems etc. An outage of any of those systems can have a financial impact that is as severe as a bug in the “main” software!
This talk gives a quick introduction into DevOps and continues to explore how test automation in operations and in infrastructure development helps to mitigate the risks associated with open collaboration between development and operations.
Based on recent developments at ImmobilienScout24 valuable lessons can be learned for every IT environment: How to to combine the goals of stable operations and quickly bringing changes into production through test automation and delivery chains.
Detailed examples can be found in this German Linux Magazin article: http://www.linux-magazin.de/Ausgaben/2014/09/Testgetrieben