I've been using Azure DevOps Pipelines for deploying an Episerver website to an Azure App Service.
My deployment to production goes like this:
- Deploy to preprod deployment slot.
- Warm up preprod, and verify that it works.
- Swap preprod with production.
- Verify that production works.
This works fine, and deployments can be done without affecting users. As long as there are no changes to the database schema or page types.
Because preprod and production use the same database. This does not work well when there are changes to the database schema.
When there are changes to page types and properties it does not work well either. Then I normally run two deploys right after one another, to get the new code deployed to both preprod and production.
Have anyone a solution to this problem?