Patterns and practices

Rolling deployments

Rolling deployments are a pattern whereby, instead of deploying a package to all servers at once, we slowly roll out the release by deploying it to each server one-by-one.

Rollbacks

Being able to roll back to a known good state of code is often just as important as deploying software.

Multi-region deployment pattern

Implementing multi-region deployments, i.e. deploying to multiple geographic regions, with Octopus.

Blue/green deployments

Blue/green deployments are a pattern whereby we reduce downtime during production deployments by having two separate production environments (“blue” and “green”).

Elastic and transient environments

Elastic and transient environments is a group of features to facilitate deploying to machines that are intermittently available for deployment.

Canary deployments

Canary deployments are a pattern for rolling out releases to a subset of users or servers.

Branching strategies

This section describes how different branching strategies can be modeled in Octopus Deploy.

Deployment process as code

With Octopus you can manage your deployment process as code. This means you can define your deployment process, scripts, and variables in source code.

Transferring packages before deployment

You can transfer packages to environments before the deployment, saving transfer time during the deployment window.