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.12 to 3.17.13

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.12 to 3.17.13.

Changes in Octopus Server 3.17.13

  • 2834 - Release Notes are now read from external NuGet feeds if the are returned
  • 3487 - NuGet packages with unsupported metadata elements in its .nuspec file no longer break package transfers
  • 3884 - Return browser security headers when viewing the communications port diagnostic page
  • 3886 - Packages used multiple times in the same project are no longer duplicated in package retention logs
  • 3905 - Server no longer blocks save of the Everyone team if the member list is out of sync with the user table
  • 3906 - Package acquisition will no longer run in parallel with manual intervention

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