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 2019.5.12 to 2019.6.5

Build information and work item tracking captures metadata about work items and build details and surfaces them with links to the appropriate sites.
Release notes templates and automatic release notes generation makes it easy to generate and share the changes that are going into your releases.
Octopus integration with Jira which provides two-way links between your Jira issues and your deployments.
Expanded Script Module support for C#, F# and Bash and Python.
Linux Tentacle early access unlocks the ability to deploy to Linux servers in highly secure environments where inbound ports cannot be opened on production servers.

Read our [Octopus 2019.6 blog post to learn more.

This release includes the following breaking changes:

There are some very slight changes to the format of the output returned by the Octopus.Server.exe show-configuration command. This functionality is unlikely to affect you, but if you are using this to drive automation, please test the new release before upgrading.
To support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
The SSH health check policy OnlyConnectivity configuration option is now a policy-wide setting. Raw scripting on SSH targets commonly uses this setting. If you are using this setting, Octopus will create a new machine policy during the upgrade. Please refer to this GitHub issue for details if this is relevant to you.

These are the features and fixes you'll get by upgrading from 2019.5.12 to 2019.6.5.

5703 - Fix for Project Deploy Release page appears to hang with a large number of tenants
5705 - Fix for incorrectly migrated user roles that could not be saved due to validation error
5708 - Create correct commit links in Octopus when using git@<host>: URLs in the VCS root in package metadata
5715 - Fix for project and project-group scoped permission UI issues
5717 - Fix for Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
5719 - Fix for Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables
5738 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log - CVE: CVE-2019-14268

5682 - Fixed an issue where server would fail to start due to incompatibility checks after upgrading from older versions
5697 - Wildfly deployments working again

5671 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
5673 - Fixed an issue where the UI would prevent you from selecting an environment to deploy to if your DeploymentCreate permissions were scoped to tenants
5675 - Deployments awaiting manual intervention will no longer block other deployments to the environment by default. This behavior can now be controlled by a switch on the manual intervention step

5665 - Fix an issue where it was not possible to select a certificate or account when using tenant variables

5663 - Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available

5651 - Added validation to the IIS configuration to ensure a hostname is entered when SNI is enabled
5650 - Show error message when kubectl returns error message