Deployment Strategy

This page explains how to customize the Deployment Strategy of the application or microservice.
For this action we use the Continuous Deployment tool to gradually roll out your application and start an automatic roll back if it's necessary.

GitHub Actions

1. In the main branch you will edit the YAML file named .github/workflows/github-ci.yaml

2. In the github-ci.yaml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

3. Bellow the section title, add the following configuration and change the values as you need:

    # Deployment Strategy
      # By default the deploys will use the rolling strategy
      # To use Canary strategy in your enviroments set this to 'true'
      strategyCanaryDev: 'false'
      strategyCanaryStg: 'false'
      strategyCanaryProd: 'false'
      # To use BlueGreen strategy in your enviroments set this to 'true'
      strategyBlueGreenDev: 'false'
      strategyBlueGreenStg: 'false'
      strategyBlueGreenProd: 'false'

4. Commit and enjoy! ✨

GitLab CI

1. In the main branch you will edit the YAML file named .gitlab-ci.yml

2. In the .gitlab-ci.yml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

3. Bellow the section title, add the following configuration and change the values as you need:

  # Deployment Strategy
    # By default the deploys will use the rolling strategy
    # To use Canary strategy in your enviroments set this to 'true'
    strategyCanaryDev: 'false'
    strategyCanaryStg: 'false'
    strategyCanaryProd: 'false'
    # To use BlueGreen strategy in your enviroments set this to 'true'
    strategyBlueGreenDev: 'false'
    strategyBlueGreenStg: 'false'
    strategyBlueGreenProd: 'false'

4. Commit and enjoy! ✨

Azure DevOps

1. In your Azure Repo's main branch you will edit the YAML file named azdevops-ci.yml

2. In the azdevops-ci.yml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

3. Bellow the section title, add the following configuration and change the values as you need:

  # Deployment Strategy
    # By default the deploys will use the rolling strategy
    # To use Canary strategy in your enviroments set this to 'true'
  - name: strategyCanaryDev
    value: 'false'
  - name: strategyCanaryStg
    value: 'false'
  - name: strategyCanaryProd
    value: 'false'
    # To use BlueGreen strategy in your enviroments set this to 'true'
  - name: strategyBlueGreenDev
    value: 'false'
  - name: strategyBlueGreenStg
    value: 'false'
  - name: strategyBlueGreenProd
    value: 'false'

4. Commit and enjoy! ✨

Bitbucket Pipelines

1. In the main branch you will edit the YAML file named .bitbucket/envs.yaml

2. In the .bitbucket/envs.yaml file search for the Features section, you will find it like this:

## Features  -------------------------------------------------------------------------------------#

3. Bellow the section title, add the following configuration and change the values as you need:

  # Deployment Strategy
  # By default the deploys will use the rolling strategy
  # To use Canary strategy in your enviroments set this to 'true'
  strategyCanaryDev='false'
  strategyCanaryStg='false'
  strategyCanaryProd='false'
  # To use BlueGreen strategy in your enviroments set this to 'true'
  strategyBlueGreenDev='false'
  strategyBlueGreenStg='false'
  strategyBlueGreenProd='false'

4. Commit and enjoy! ✨

warning

Deployment Strategies is only available for NGINX Ingress.