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.8.6 to 2019.9.1

Octopus 2019.8

Highlights

2019.8 includes:

  • Improved deployment process editor: Quickly jump between steps when editing the deployment process
  • Cloning Tenants
  • More health check scheduling options: Health checks can be configured to run on a cron expression, or to never run
  • Allow overriding namespace in Kubernetes steps
  • New Variable Filter expressions: Trim, Substring, Truncate, UriEscape, UriDataEscape
  • Copy and paste to add certificates: Certificates can now be pasted as text directly into the portal

See our blog post for the full details.

Breaking changes

No breaking changes in this release

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.9 LTS

Highlights

  • Streamlined deployment process editor with better visibility of your entire deployment process and fewer clicks to navigate between steps.
  • Added support for Tentacle for Linux to improve the flexibility of Linux deployments including support to deploy to highly secure environments where it’s not possible to open port 22.
  • Tenant cloning for faster configuration of new Tenants.
  • Added health check scheduling options so they can be configured to run on a cron expression, or to never run.
    • Added support to override namespace in Kubernetes steps.
    • New Variable Filter expressions including Trim, Substring, Truncate, UriEscape and UriDataEscape.
    • Added support to paste to certificates as text to add certificates directly in the portal.

Read our blog post to learn more.

Breaking changes

This release includes a single breaking change as Octopus Server no longer supports for Windows Server 2008 SP2.

Tools

This release bundles the following command line tools and frameworks:

  • AWS CLI - 1.16.178
  • AWS PowerShell Cmdlets - 3.3.390
  • Azure CLI - 2.0.50
  • Azure Powershell Cmdlets - 6.13.1
  • Terraform CLI - 0.11.8
  • Terraform AWS provider - 1.39.0
  • Terraform Azure provider - 0.1.1
  • Terraform AzureRM provider - 1.17.0

Details

Changes in Octopus 2019.8.6

  • 5797 - Fixed how manual interventions are handled when they occur during a deploy release step
  • 5835 - Account parameters used in Step Templates are now expanded, making them easier to use
  • 5851 - Shows cleaner exception message when executable is not found in steps with script logic
  • 5866 - Fixed an issue that caused certain steps to now show in the channel version rule selector
  • 5868 - Fixed comparison of package ids between build information and steps to be case insensitive
  • 5872 - Improved validation and error messsages for Automatic Release Creation package steps
  • 5874 - Improve reliability of temp file handling on Linux targets and avoid silent failure of "Deploy to NGINX" steps
  • 5878 - Removed duplicate email validation when modifying or registering users

Changes in Octopus 2019.9.0 LTS

  • 5755 - Added informational message on how to work around PowerShell terminating processes on Win2019 and .NET 4.7.2 when an error is output
  • 5824 - Project logos are now copied when a project is cloned
  • 5880 - helm init in the Helm Upgrade step no longer refreshes the local repository cache
  • 5883 - Fix for Kubernetes node affinity not being set during deployment
  • 5889 - Project overview screen is no longer dependant on LibraryVariableSetView permission for Tenanted projects

Changes in Octopus 2019.9.1 LTS

  • 5894 - Create User action can now add external logins, due to a bug was only available in editing existing users
  • 5896 - Fixes rare crash in editing a package deployment step if a large amount of feeds are present

Welcome! We use cookies and data about how you use our website allow us to improve the website and your experience, and resolve technical errors. Our website uses cookies and shares some of your data with third party analytics companies for these purposes. We do not use these cookies for advertising.

If you decline, we will respect your privacy. A single cookie will be used in your browser to remember your preference.