Continuous delivery (CD) is a set of practices that aims to build, test, and release high quality software frequently and reliably. It is based on automating the software delivery process, including integrating, testing, and deploying code changes. The key principles of CD are automating builds, deployments, testing, and having everyone responsible for the release process. This reduces risk and allows teams to get feedback faster through more frequent releases of working software.

1. [email_address] 020 3206 1900

2. Continuous Delivery Ifor Evans Head of Platform Development, Betfair Continuous Delivery

6. Principles of CD Build artefacts only ONCE Use the same automated mechanism to deploy to EVERY environment Smoke test your deployment If anything fails, STOP the line EVERYBODY has responsibility for the release process - Code, DB, Config & System config changes Principles of CD

8. Continuous Delivery vs Continuous Deployment Continuous Deployment means that every build that passes all automated tests will be deployed to Production. Scary? Continuous Delivery allows managed deployments and release windows. Bit less scary? Giving control of releases to the business. Continuous Delivery vs Continuous Deployment

9. Prerequisites Automated Builds Automated Static Code Analysis Automated Unit Tests (code & db) Automated Functional Tests (code & db) Automated Security Tests Automated Performance Tests Automated System Integration tests Automated Sanity/Smoke Tests Automated Deployments & Configuration Automated VM Provisioning Automated Network Provisioning Prerequisites

14. END 020 3206 1900 [email_address]