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.17.11 to 3.17.12

Octopus 3.17

Changes in 3.17

See our release blog post for more details.

New Features

Octopus 3.17 introduces first-class Java support so teams can start deploying their Java apps in a safe, repeatable and reliable way! This release includes support to deploy to Tomcat, RedHat JBOSS EAP and Wildfly application servers and the Octopus built-in repository can now manage Java packages like jar, war, ear and rar files.

Improvements

  • Swagger support for the Octopus API
  • Improved user administration and authentication performance

Breaking Changes

There are no breaking changes in this release.

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

Release notes

These are the features and fixes you'll get by upgrading from 3.17.11 to 3.17.12.

Changes in Octopus Server 3.17.12

  • 3839 - Fixed swagger.json using ints instead of strings for enums
  • 3848 - Added operationId to swagger document for better code gen
  • 3895 - Script module files now gets cleaned up after being imported by the PowerShell bootstrap script
  • 3896 - Variable substitution works now with JSON files that have an array as the root object
  • 3899 - Resolved issue introduced in 3.17.11 where Release Assembled date was being set to the beginning of time when created via octo.exe

Changes in Octopus Server 3.17.11

  • 3682 - Resolved issue where Octopus Manager was not correctly binding 'Include Task Logs' option when migrating 2.6 backups
  • 3792 - Added CommonName certificate variable
  • 3800 - When creating a Release, if Assembled date supplied then use it
  • 3855 - Resolved issue when migrating ServerTask with single MachineId where array was expected
  • 3885 - Fix for Octopus.Server.exe admin command passing email to display name field when creating a user, resulting in blank email