Automated updated processes that integrate with your DevOp workflows

Automated Drupal updates and security updates in particular have been discussed on Drupal.org. As a result an "auto update feature" in Drupal core will not work due to the lack of integration with development and deployment processes. Nevertheless Drupalgeddon proofed that Drupal needs automated updates to keep millions of sites secure in case critical security issues appear.
Using professional development tools such as testing frameworks, continuous integration, deployable containers and tools for automation, it is not that hard to use or build an infrastructure to automate Drupal updates "from the outside".

In this session I want to show which components are needed to automate Drupal updates in a professional environment. I will also highlight, how and why an integration with existing development and deployment workflows is needed to ensure quality. In particular I want to give answers to the following questions_

• How to handle different types and criticalities of updates
• How to deal with patches when automating updates
• Why feature branches are a good way to deploy updates fast
• How to avoid being hacked with continuous update deployment
• Requirements to the hosting and development infrastructure
• How to avoid automated updates breaking your site's functionality after

This session will leave some space for discussions an that topic.