Continuous Deployment explained in code

Continuous Deployment (CD) is the process where code pushed to a target branch automatically goes through testing and deployment stages without any manual intervention. This can be done on staging or testing servers before reaching production. In this text, Don Brown explains how they use continuous deployment at Sleuth using Circle CI for RCI (Continuous Integration). The company's codebase contains a directory called .circleci with a file named config.yml that holds the CI and CD workflows. The workflow runs on every push to a branch not named master, executing tasks such as running tests or building Docker images. For full continuous deployment, they add jobs like deploying to staging or production servers. The setup-aws-credentials command is used to configure AWS with the necessary API keys and information for deployment. Sleuth uses Amazon Fargate to deploy services in Docker containers. Before deploying the app, they run any database migrations using a new Docker container. Finally, Sleuth tells itself about the deployment so it can visualize and track its health across multiple environments.