Continuous Delivery is a deployment automation practice in which every single change to code is made on the main branch in the repository (usually 'master') and immediately built, tested and deployed. Whereas both the tests and the deployments are fully automated, the release to the production server requires an additional manual confirmation.
Introducing Continuous Delivery to your project requires the application to be thoroughly covered with tests and a properly trained team with established work culture.
Continuous Delivery pipeline
The basics of Continuous Delivery are essentially the same as of Continuous Deployment and thanks to Buddy, creating a delivery automation pipeline is easier as ever. The best idea is that you start with building a delivery pipeline described here.
To turn a Continuous Deployment pipeline into a Continuous Delivery pipeline, it should stop immediately after the automatic build and tests and wait for a manual release confirmation: Continuous delivery process
To achieve that in Buddy, you should use the Wait for approval action: Wait for Approval action location
The action lets you define who can confirm the latest version. You can restrict the permission to a specific team member or a group: Action configuration
Make sure to add a notification action that will inform authorized team members about a new version waiting to be released. It should be placed just before the approval action in the pipeline.
Buddy offers a wide variety of notifications. You can use a dedicated Slack, Discord or Telegram integration, or send messages via email or SMS: BUddy notification actions
A properly configured Continuous Delivery pipeline should look like this: Buddy pipeline example
A pipeline prepared this way will be run automatically after each push to the main branch. It will also test the application and prepare it for the release. After that, it needs to be confirmed manually.
Last modified on September 8, 2022