Compare releases

Compare releases

Find out what's new in the latest Octopus Deploy release, or compare the latest release to what you're currently running to see what's changed.

Highlights

These are the most important features you'll get by upgrading from 2019.6.3 to 2019.7.1

Octopus 2019.6 LTS

Highlights

  • 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-LTS blog post to learn more.

Breaking changes

This release includes some minor breaking changes:

  • There are some slight changes to the format of the output returned by the Octopus.Server.exe show-configuration command. This is unlikely to affect teams, but if you are using this to drive automation, please test the new release before upgrading.
  • In order to support some customers who have Active Directory configurations where users share email addresses, we have removed 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 OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting, a new machine policy will be created during the Octopus Server upgrade.

Tools

This release bundles the following command line tools and frameworks:

  • AWS CLI - 1.16.178
  • AWS PowerShell Cmdlets - 3.3.522
  • AWS Azure CLI - 2.0.50
  • AWS Powershell Cmdlets - 6.13.1
  • Terraform CLI - 0.11.13
  • Terraform AWS provider - 2.8.0
  • Terraform Azure provider - 0.1.1
  • Terraform AzureRM provider - 1.27.1

Octopus 2019.7

Highlights

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.

Tools

This release bundles the following command line tools and frameworks:

  • AWS CLI - 1.16.178
  • AWS PowerShell Cmdlets - 3.3.522
  • AWS Azure CLI - 2.0.50
  • AWS Powershell Cmdlets - 6.13.1
  • Terraform CLI - 0.11.13
  • Terraform AWS provider - 2.8.0
  • Terraform Azure provider - 0.1.1
  • Terraform AzureRM provider - 1.27.1

Details

Changes in Octopus 2019.6.3 LTS

  • 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

Changes in Octopus 2019.6.4 LTS

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

Changes in Octopus 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 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