Migrate to cloud: Define the deployment strategy

Edit on GitHub

After you have provisioned the Spryker Cloud Commerce OS environments, you have to define the deployment strategy.

The current Spryker Cloud Commerce OS solution doesn’t support advanced rollout strategies like blue-green deployments and canary deployments. Therefore, it’s necessary to conduct thorough testing before implementing changes in a production environment.

Within CodePipeline, there are several deployment types:

  • Build: Used solely for image verification during the building process and does not involve any rollout.
  • Rollout Scheduler: This pipeline specifically handles the deployment through Jenkins.
  • Normal: The primary pipeline for application deployment.
  • Destructive: Similar to the Normal pipeline but includes the process of clearing and then populating data in the RDS. This pipeline is mandatory for the initial deployment or when data needs to be refreshed.

For more information about deployment process and its states, see Deployment in states.

Next step

Define environment variables