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.10.9 to 2019.10.11

Octopus 2019.10

Highlights

Flexible Linux deployments, PowerShell Core support, Operations RunBooks EAP

  • Tentacle for Linux enables deployments to highly secured servers without opening port 22 in production environments
  • Built-in PowerShell Core support for both Windows and Linux platforms
  • Improved build information and work item tracking
    • Package metadata has been renamed to Build Information and promoted to a top level section in the Octopus Library.
    • Added support for deployment change templates so you can customize the structure of your deployment changes.
  • Simpler package-based step templates whereby we show our package selector when a package-based step template is added to a project
  • Early access to Runbooks for Operations teams enabling teams to run emergency or routine operations tasks in a first-class way

Read our blog post to learn more.

Breaking changes

PowerShell Core

PowerShell Core support has introduced a change where running PowerShell scripts against non-Windows targets no longer silently ignores .ps1 files. Octopus will now attempt to execute .ps1 files on deployment targets. If PowerShell Core is installed on those targets, this may change the behaviour of your deployments. If PowerShell Core is not installed on those targets, the deployment will fail.

Build Information

Our build information change involved renaming resources from the API through to the database. This is generally backwards compatible, however anyone using our GitHub issue tracker will need to ensure they upgrade their Octopus Server if they upgrade their Azure DevOps extension, TeamCity plugin, or Bamboo plugin.

Release notes

These are the features and fixes you'll get by upgrading from 2019.10.9 to 2019.10.11.

Changes in Octopus Server 2019.10.11

  • 3765 - The start time for targets in rolling deployments is now shown correctly in the log headers
  • 6035 - Reduce network IO usage in Windows listening tentacles
  • 6037 - Fixed db query to improve speed of task event query

Changes in Octopus Server 2019.10.10

  • 6036 - Option to not re-deploy release for scheduled trigger with "deploy latest release" action
  • 6042 - Fix on screen error for channel creation

Changes in Octopus Server 2019.10.9

  • 4559 - Fixed bug causing new targets to not be included in deployments when targets are re-included by the same health check
  • 5945 - Update the Jira Issue Tracker test button to do a more thorough check of the user's permissions and ability to read work items
  • 6010 - Fixed race condition when selecting tenants or tags when creating a release possibly causing the wrong deployment to be shown
  • 6015 - Added a UriPart function to Octostache
  • 6023 - Fixed issue in health checks where machines were not correctly re-included into the deployment
  • 6024 - The Deployments and Operations menus within a project now always remain open
  • 6025 - Fixed bug that was excluding targets from deployments if they were "healthy with warnings"
  • 6026 - Fixed dropdown "select as you type" functionality
  • 6027 - Fixed a bug where connections may have been opened unnecessarily when querying the /api/projects/all endpoint
  • 6031 - Fixed a regression with force package deployment that was introduced in 2019.10