Compare releases

Compare releases and check for compatibility between your existing Octopus Server and new releases.

→

What's new

These are the most important features you'll get by upgrading from 3.2.24 to 3.3.1

Octopus 3.3

New Features in 3.3

  • Script-steps can source the script from a package
  • Script-steps can execute on the Octopus server without requiring a Tentacle
  • Server-based steps (i.e. email, manual-intervention, and the new server-script steps) can be child steps
  • Support for zip and tar packages
  • OctoPack.js + gulp and grunt wrappers Guide for deploying Node.js
  • Azure Service Principal account type
  • Azure Resource Group Template step type
  • ASP.NET 5 (Sorry, ASP.NET Core) JSON configuration support
  • Breaking change: Sensitive Properties have changed to resolve a number of issues on deployment steps and templates, affecting octo.exe, Octopus.Client and the TeamCity plugin (see below for more details)

Read our blog post announcing 3.3

Please Note: you will need to upgrade octo.exe, Octopus.Client and the TeamCity plugin when upgrading to Octopus Deploy 3.3

Breaking Change: Sensitive Properties

As part of this release we have resolved a number of minor issues with sensitive properties on deployment steps and step templates. The issues resolved include:

  • Windows Service Custom account and password properties no longer retained when switching account types (#2264).
  • Sensitive fields in steps can now be cleared/reset (#2311)
  • Username/password fields on IIS and Windows Service features will remain visible if account-type/identity is bound to a variable (#2333)
  • Sensitive fields now use a consistent UI control across the entire portal.

Breaking Change

This introduces a breaking change to our API, and will affect those using the following endpoints:

  • /api/deploymentprocesses
  • /api/actiontemplates

It also affects octo.exe, Octopus.Client and the TeamCity plugin. If you are using any of these components please upgrade them when upgrading to Octopus Deploy 3.3.

See Sensitive Property API Changes in Release 3.3 for more details.

Upgrading

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

Please upgrade octo.exe, Octopus.Client and the TeamCity plugin when upgrading to Octopus Deploy 3.3.

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.

Release notes

These are the features and fixes you'll get by upgrading from 3.2.24 to 3.3.1.

Changes in Octopus Server 3.3.1

  • 2376 - Fixed scenarios that were failing when the host server is required to be FIPS 140 compliant
  • 2390 - On-screen help text added to Azure PowerShell step explaining Service Management cmdlets can't be used with Service Principal accounts and Resource Manager cmdlets can't be used with Management Certificate accounts
  • 2395 - Immediately executing code in Script Modules now have access to Octopus Variables
  • 2398 - Exporting a step template is now prevented until any changes are saved
  • 2402 - Fixed an issue that was preventing Calamari from updating on multiple SSH endpoints due to a file lock

Changes in Octopus Server 3.3.0

  • 641 - Email, Manual Steps and Azure Powershell steps can now be executed in a rolling step. Also added support to run a PowerShell Script on the Octopus Server.
  • 2069 - Enable Azure Active Directory auth for Azure Accounts
  • 2091 - Show warning if file is missing during config transformation
  • 2133 - Azure Resource Group deployment step type
  • 2183 - Support .zip and .tar.gz package formats
  • 2189 - Script step embedded in a NuGet package
  • 2304 - Support for ASP.NET Core

Changes in Octopus Server 3.3.0-beta0002

  • 2345 - Corrected instructions for pushing packages via the api to the built-in repository
  • 2354 - Improve the error message when using the JSON config feature and a folder is specified as the target file
  • 2355 - Delete parameters that have been renamed/removed from the action properties collection
  • 2356 - The selected Resource Group in the “Deploy an Azure Resource Group” step now binds correctly when editing an existing step
  • 2357 - The display of long parameter names for Azure Resource Manager templates will now wrap instead of overflowing underneath the input control
  • 2359 - The display of Web Apps in the select list has been updated to display the Region and Resource Group (where available)
  • 2363 - The http://ASP.NET|ASP.NET Core JSON AppSettings feature is now the JSON configuration variables feature
  • 2364 - JSON config feature only replaces variables it can find instead of inserting all available project variables
  • 2374 - Invoke Set-AzureRmContext when authenticating with service-principal

Changes in Octopus Server 3.2.24

  • 2231 - The Active Directory user groups cache will now be invalidated for a user when they explicitly Sign Out from the Octopus Server, forcing a foreground refresh on their next Sign In
  • 2318 - Added ability to delete Octopus Server high-availability nodes via the API
  • 2334 - The Octopus data importer/migrator is now more reliable when detecting duplicate historical data with key collisions
  • 2362 - Updated the Octopus Server node screen to properly report task counts
  • 2384 - Fixed open redirect bug in the Octopus web portal integrated authentication process