[#172123296] pipeline support to deploy using staging slot #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following changes have been implemented in the Azure DevOps pipeline to address zero downtime & fast rollback in production:
added support for selecting one of the following deployment methods in production environment:
Note 1. The default value is now set to deployToProductionSlot to allow developers to continuously deploy in the current infrastructure (without slots). We can change the default to deployToStagingSlot when the 'staging' slot with 'auto swap' on will be available.
Note 2. The deployment to a slot (e.g. 'staging') could automatically trigger the swapping with 'production' slot if "auto swap" will be enabled in the App service configuration. This also means that if the "auto swap" is on and you select 'deployToStagingSlotAndSwap' to swap 'staging' and 'production' slots after deploying to 'staging', the swap task in this pipeline will fail because conflicting with another (automatic) swap operation in progress.
[not used] added for experimental purpose only the support for the following deployment methods in test environment (now not available):
Note 3. Today we still do not have a test environment and for this reason the deployment in the test environment is currently disabled by default. The definition of this environment, useful for executing integration tests, is a work in progress but the idea is to have a separate and dedicated slot ('slot').
improved our Azure pipeline with the new Runtime Parameters to make it easier and faster to set some configuration settings that can be passed when manually running the pipeline; e.g. now you can select the deployment environment and mode directly in the main "Run pipeline" panel of the Azure DevOps portal (the previous pipeline took you three clicks to modify a single value for every single variable and for every run):