Have you ever wondered why many deployments are still manually released, even though they often contain only a few pieces of information and serve little as a real safeguard? If you are using ring-based deployments, it is even more important to increase the level of automation and not rely on manual releases. This is where gated releases come in.

Gated releases allow you to check various signals before transferring the application to the next environment. This includes system states such as processor, RAM, and I/O, unhandled exceptions in log files, or completed processes. With gated releases, you have the opportunity to fully automate the release process and take your continuous deployment to the next level.

In this practical lecture, Thomas shows you how to implement fully automated gated releases for ring-based deployments using GitHub Actions and the GitHub API. This lecture is aimed at DevOps engineers and developers who want to improve and optimize their release pipelines.

My session can deliver from 45min to 60min of content. It is aimed at developers as well as "DevOps Engineers" or similar.
Since I want to include a demo with hardware as a showcase (can, not must) I need some space [about A3 area]. Since Github is now a very important platform for development, and gated releases are not yet available OutOfTheBox in GitHub, this will be a very valuable session for the participants - especially those from the enterprise sector.