Course contentsShow
← Cloud and Infrastructure
Lesson 1767 of 2,98936. GitLab CI/CDFree lesson

Deployment Strategies and Environments

Implement canary, blue-green, and incremental rollout strategies with environment-specific deployments.

Deployment Strategies and Environments

You'll learn how to implement canary, blue-green, and incremental rollout strategies using GitLab's environment-specific deployment features.

Core Concept

Deployment strategies control how new application versions reach users. GitLab CI/CD lets you define named environments (like production, staging, canary) and deploy to them with different risk-mitigation strategies:

Blue-Green Deployment: Maintain two identical production environments. Deploy to the inactive "green" environment, test it, then switch traffic from "blue" to "green" instantly. If issues arise, switch back immediately.

Canary Deployment: Roll out changes to a small subset of users first (the "canary"). Monitor metrics, and if healthy, gradually increase the percentage until everyone receives the new version.

Incremental Rollout: Similar to canary but more structured—deploy to 10% of infrastructure, then 25%, 50%, 75%, and finally 100%, with manual or automatic gates between stages.

GitLab Implementation Pattern

Define multiple jobs targeting the same logical environment but with different deployment scopes:

deploy_canary:
  stage: deploy
  script:
    - deploy.sh --percent=10
  environment:
    name: production/canary

deploy_production:
  stage: deploy
  script:
    - deploy.sh --percent=100
  environment:
    name: production
  when: manual
  needs: [deploy_canary]

The environment keyword tracks deployments in GitLab's UI. Use when: manual for gates requiring approval. Combine with rules to automate progression based on conditions like successful health checks or time delays.

Environment-specific variables and protection rules ensure only authorized pipelines deploy to sensitive environments like production.

Key Takeaway: GitLab's environments and deployment jobs enable safe, phased rollouts—canary tests with small user groups, blue-green provides instant rollback, and incremental spreads risk across infrastructure gradually, all tracked visually in your CI/CD interface.