Exploring Deployment Jobs strategies in Azure DevOps multi-stage YAML – Rolling Deployment

Exploring Deployment Jobs strategies in Azure DevOps multi-stage YAML – Rolling Deployment

A Rolling Deployment strategy in Azure DevOps involves deploying updates incrementally to one environment at a time, moving from lower environments to higher environments (e.g., Development → Staging → Production).

This allows for gradual validation and testing before the changes are fully deployed.

Key Concepts of Rolling Deployment

1. Incremental Deployment: Deploying updates to one environment at a time while ensuring stability in previous environments.

2. Traffic Shifting: Gradually moving traffic from the old environment to the new environment as updates are deployed.

3. Progressive Validation: Ensuring that lower environments are stable before proceeding to higher environments.

Example Multi-stage YAML with Rolling Deployment Strategy

xxxxxxxxxx
21
1
stages:
2
  - stage: Dev
3
    jobs:
4
      - job: DeployDev
5
        steps:
6
          - script: echo "Deploying to Development environment..."
7
          - script: echo "Testing in Development..."
8
  - stage: Staging
9
    dependsOn: Dev
10
    jobs:
11
      - job: DeployStaging
12
        steps:
13
          - script: echo "Deploying to Staging environment..."
14
          - script: echo "Testing in Staging..."
15
  - stage: Production
16
    dependsOn: Staging
17
    jobs:
18
      - job: DeployProduction
19
        steps:
20
          - script: echo "Deploying to Production environment..."
21
          - script: echo "Validating in Production..."

Details of Rolling Deployment Strategy

1. Dev Stage:

   • Deploy updates to the Development environment.

   • Perform testing to ensure stability.

2. Staging Stage:

   • After Dev is stable, move to Staging.

   • Ensure proper validation and testing in Staging.

3. Production Stage: Once Staging is validated, deploy to Production with minimal risk.

Steps in Rolling Deployment

1. Deploy to Development:

   • Apply updates to the Development environment.

   • Run unit tests and basic validations.

2. Deploy to Staging:

   • After Development is stable, deploy to Staging.

   • Conduct more comprehensive testing.

3. Deploy to Production: Finally, deploy updates to Production after ensuring that Development and Staging environments are stable.

Additional Considerations

1. Traffic Management: Gradually shift traffic from old environments to new ones to minimize impact.

2. Testing: Conduct extensive testing at each stage to ensure quality.

3. Rollback: Prepare rollback strategies in case issues arise at any stage.

4. Notifications: Use notifications at each stage to inform stakeholders about progress and deployment status.

Using Approval Gates in Rolling Deployment

You can combine Rolling Deployment with Approval Gates to ensure manual intervention at key stages.

xxxxxxxxxx
29
1
stages:
2
  - stage: Dev
3
    jobs:
4
      - job: DeployDev
5
        steps:
6
          - script: echo "Deploying to Development..."
7
          - script: echo "Testing Development environment..."
8
          - hooks:
9
              - approval:
10
                  name: Dev Approval
11
                  condition: eq(variables['Build.Status'], 'Succeeded')
12
  - stage: Staging
13
    dependsOn: Dev
14
    jobs:
15
      - job: DeployStaging
16
        steps:
17
          - script: echo "Deploying to Staging..."
18
          - script: echo "Testing Staging environment..."
19
          - hooks:
20
              - approval:
21
                  name: Staging Approval
22
                  condition: eq(variables['Build.Status'], 'Succeeded')
23
  - stage: Production
24
    dependsOn: Staging
25
    jobs:
26
      - job: DeployProduction
27
        steps:
28
          - script: echo "Deploying to Production..."
29
          - script: echo "Validating Production environment..."

Summary

A Rolling Deployment strategy in Azure DevOps helps ensure a gradual and controlled deployment process, minimizing risk and improving overall system stability. Write in comments and let me know if you’d like more details or examples.