Compare releases

Compare releases

Find out what's new in the latest Octopus Deploy release, or compare the latest release to what you're currently running to see what's changed.

Highlights

These are the most important features you'll get by upgrading from 3.1.7 to 3.2.0-beta0001

Octopus 3.1

Highlights and new Features of 3.1

  • Azure support revisited - blog post
  • TLS 1.2 (Requires Tentacle 3.1) - blog post
  • Reporting - blog post
  • Breaking change: Due to the dependency on .NET 4.5 Octopus Server and Tentacle 3.1 are no longer supported on Windows Server 2003 or Server 2008 SP1 - more information

Read the blog post for more details on the changes and features introduced in Octopus 3.1.

Upgrading Tentacles: You can upgrade to Octopus Server 3.1 without upgrading any Tentacles and get all of the new 3.1 deployment features because Calamari will continue to work on both Tentacle 3.0 and 3.1 - more information

Read the upgrade guide for more details on upgrading from your current version to Octopus 3.1.

Octopus 3.2

Highlights and new Features of 3.2

Octopus Deploy 3.2 is all about Channels and is a highly-compatible feature release with no breaking changes. Channels is the name we've given to the feature originally discussed in our RFC on Branching.

Build servers build. Octopus deploys.

We decided it was important to drive a distinction between source code branches, which build servers care about, and deployment, which is where Channels come in.

Read the upgrade guide for more details on upgrading from your current version to Octopus 3.2.

Details

Changes in Octopus 3.1.7

  • 1890 - By default bind Tentacles to both IPv6 and IPv4 address to allow communication over both protocols
  • 2106 - File operation errors (such as copying files) will fail the deployment
  • 2107 - Removed useDefaultProxyCredentials from config file which was causing Calamari to crash upon starting under mono.