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 3.15.7 to 3.15.8

Octopus 3.15

Changes in 3.15

New Features

This month, we bring you some much requested improvements to multi-tenant deployments, as well as Octopus Server integration with Let's Encrypt and more!

The way machines, accounts and certificates participate in tenanted-deployments can now be explicitly specified. This includes allowing un-tenanted projects to be deployed to tenanted machines. This has been a long-standing gripe with tenanted deployments which we're very happy to resolve.

Our new integration with Let's Encrypt means you can setup an SSL certificate for your Octopus Portal and it will automatically be renewed when it expires. No need to worry about buying a certificate or manually reconfiguring your server.

Read the full post on the Octopus blog.

Improvements

  • If you're automating the setup of the Octopus Server or Tentacles, you'll be happy to hear that we've put some solid effort into cleaning up our console logging. It will now be much easier to get the information you need without having to do string parsing.
  • Granting Edit permissions now automatically assigns View permissions. It always helps to be able to see what you're changing.

Breaking Changes

  • Console output has changed (for the better!), so we advise testing any automation before upgrading to this version.
  • Octopus.Client version 4.19.0 contains API changes corresponding with the multi-tenant deployment participation change, a minor breaking change for anyone using the MultiTenantDeploymentMode on Project resources via the client.

Upgrading

This release contains a post-install data fix that may take some time (depending on the size of your Events table), so please ensure you allow time for this to complete. If you are running the watchdog service, please ensure this is stopped during the upgrade.

As always, read the upgrade guide for more details on upgrading to Octopus 3.15.

Release notes

These are the features and fixes you'll get by upgrading from 3.15.7 to 3.15.8.

Changes in Octopus Server 3.15.8

  • 3522 - Add audit events when a package is deleted from the built-in repository and keep 1 weeks worth of package repository retention logs
  • 3630 - The --console switch is no longer required by scripts automating the Octopus or Tentacle command-line interface, but is still supported for starting either service interactively if so desired
  • 3665 - Fixed a bug that would sometimes result in a null reference exception when setting a password in a step
  • 3675 - Life Cycle listing in the Library will now be available to those with permission LifecycleView, it used to require LifecycleEdit
  • 3678 - Fixed a bug which was preventing the task list from being filtered by Server Node after upgrading to Octopus 3.15.x
  • 3680 - Corrected Azure account variables masking in log
  • 3681 - Add an audit event when the server retention policy deletes a release
  • 3686 - Ensure 'restart required' message is shown for all relevant configure commands
  • 3687 - Improve error message when Docker feed test cant connect successfully

Changes in Octopus Server 3.15.7

  • 3629 - You can now filter audit events for specific tenants
  • 3666 - Fixed a problem which could cause a SQL Connection leak when synchronizing Active Directory groups under certain circumstances
  • 3669 - Fixed a problem where certificate variables were not being scoped by tenant tags
  • 3671 - Default value of sensitive project variable templates is now preserved between updates
  • 3762 - Using our production certificate when signing the Tentacle files in TeamCity
  • 3674 - Fix for ids filtering in projects, tenants and library-variable-sets API