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.6.6 to 2019.7.7

Octopus 2019.7


Octopus 2019.7 is a significant release even though it doesn't include any user-facing features. It includes technical changes to retarget Octopus Deploy to .NET Framework 4.7.2 and .NET Core 2.2 so Octopus can run natively on Linux and in Linux containers. This change is initially for Octopus Cloud and it will be extended to Octopus self-hosted in the future.

Watch our blog for some great technical blog posts on what this involved and our lessons learned.

Breaking changes

Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.

Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.

Octopus 2019.6


  • 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.

Breaking changes

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.

Release notes

These are the features and fixes you'll get by upgrading from 2019.6.6 to 2019.7.7.

Changes in Octopus Server 2019.7.7

  • 5590 - Allow overriding namespace in Kubernetes steps
  • 5607 - Internal mapping improvements to increase tenant variable set endpoint
  • 5750 - Tentacle TentacleProxyPassword logged in clear text when OctopusPrintVariables is set
  • 5751 - Fix for partialName parameter searching on the artifacts API endpoint
  • 5761 - TentacleProxyPassword logged in clear text if $env:HTTP_PROXY is printed and password contains special characters
  • 5764 - Support providing certificates via porta by directly pasting as text

Changes in Octopus Server 2019.7.6

  • 4418 - Deploy a Release steps can now be used in rolling deployments
  • 5620 - UI fixing anchor-links in the task summary list
  • 5713 - Automatic health checks can now be disabled or scheduled using a cron expression
  • 5729 - Fix issue with "all nodes offline" when a new instance is setup against an existing database
  • 5754 - Fixed some sensitive value handling in the server config API/portal UI - CVE: CVE-2019-14525

Changes in Octopus Server 2019.7.5

  • 5709 - S3 Special Header Content-Type not being set properly
  • 5723 - Improved parsing of Jira issue references, and only display Jira issues that exist in the configured Jira instance
  • 5725 - Updates to Audit Filtering
  • 5744 - Fixed an issue where UI feature toggles were misbehaving
  • The following issues were rolled forward from 2019.7.4 release (that was pulled due to a feature toggle issue):
  • 5406 - Migrator import command won't load variable sets associated with deployments
  • 5732 - Update Dashboard to fix bug in configuring limited rows
  • 5734 - Library Variables Sets are now displayed again
  • 5735 - Fix an issue where multiple overflow menus can be open at the same time
  • 5740 - Fixed a bug where you could not search for Docker images using DockerHub external feeds

Changes in Octopus Server 2019.7.3

  • 4394 - Improved the variable preview screen to make it clearer how it works and ensured all variable types were displayed correctly
  • 5634 - Fixed disposing of leases for external workers with packages
  • 5652 - Added default roles for build servers
  • 5704 - Fixed license check code to deduplicate tentacles and ssh endpoints
  • 5707 - Create correct commit links in Octopus when using git@<host>: URLs in the VCS root in package metadata
  • 5710 - Fix for project and project-group scoped permission UI issues
  • 5714 - Fix for DeploymentQueued event not being created with ARC
  • 5720 - Fix for Project Deploy Release page appears to hang with a large number of tenants
  • 5739 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log - CVE: CVE-2019-14268

Changes in Octopus Server 2019.7.2

  • 5617 - Increased timeout for downloading external NuGet feeds from 60s to 1hr
  • 5668 - Prompted variables are now ordered alphabetically when creating a deployment
  • 5681 - Allow library step templates to be deleted when referenced in releases
  • 5686 - In some cases the task progress percentage was not reported in the log
  • 5689 - Resolved issue where extracting template from deployment step could result in ‘Given key not present in dictionary’ error
  • 5692 - Fix issue where changing tabs in a library step template based on a script step would error when choosing to to use a script in a package
  • 5696 - Added helper functions to write progress bar messages to the deployment log
  • 5698 - Update UI and calculation of matched records on dashboard
  • 5699 - Sensitive variables in step properties are no longer cleared when a step is enabled
  • 5701 - Fix for incorrectly migrated user roles that could not be saved due to validation error
  • 5716 - Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
  • 5718 - Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables

Changes in Octopus Server 2019.7.1

  • 5509 - Adding friendly landing page for users with no permissions to see Environments
  • 5667 - UI adding configuration to control features of the help sidebar
  • 5678 - Hidden folders are now ignored when migrating to Spaces new packages folder structure
  • 5679 - Fixed an issue where server would fail to start due to incompatibility checks after upgrading from older versions
  • 5684 - Update msi installer to check for .NET 4.7.2
  • 5685 - UI adding actions to add another target/worker for easier data entry

Changes in Octopus Server 2019.7.0

  • 4802 - Added validation to the IIS configuration to ensure a hostname is entered when SNI is enabled
  • 5503 - Show error message when kubectl returns error message
  • 5504 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
  • 5602 - Fixed paging on the user activity feed
  • 5642 - Clarified error message shown when a recursive variable definition is detected
  • 5645 - Fix for team deletion issue with email steps
  • 5646 - Removed ProjectGroupId from Deployment as this was not being kept in sync during Project moves (to other project groups), and causing octo.exe to fail to import
  • 5653 - Accounts referenced by targets used in a deployment manifest are now shown in account usage
  • 5654 - Made displaying usage more consistent and performant
  • 5656 - Fixed dirty state checking on Deploy an ARM Template step
  • 5657 - Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available
  • 5658 - Account usage for Token, Username/Password and SSH Key Pair account types now show all available usage types, not just usage in targets
  • 5659 - Consolidated release usages and release snapshot usages for account types for clarity
  • 5660 - Added the ability to delete a specific deployment
  • 5664 - Fix an issue where it was not possible to select a certificate or account when using tenant variables
  • 5666 - 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
  • 5669 - Fixed an issue where the UI would prevent you from selecting an environment to deploy to if your DeploymentCreate permissions were scoped to tenants

Changes in Octopus Server 2019.6.6

  • 5724 - Improved parsing of Jira issue references, and only display Jira issues that exist in the configured Jira instance (requires a username and password to be configured on the Jira issue tracker settings page)
  • 5753 - Fixed some sensitive value handling in the server config API/portal UI - CVE: CVE-2019-14525