The Machine Protection Software Team has been using a Continuous Delivery workflow for numerous years, covering shutdown and physics activities of the LHC. This continuous delivery workflow relies on numerous practices that are necessary to ensure the automated validation of the software products: unit tests, automated user acceptance tests, static code analysis, quality tracking, etc. This workflow brings ease and confidence for the deployment of the software products. Some challenges are however left unaddressed for the time being, like how to integrate a continuously delivered set of dependencies into a product that doesn’t implement continuous delivery. We propose to present the implementation of the continuous delivery workflow, its outcomes for the development team and for the product users, and the current limitations and the questions that are left unresolved.