Compare releases

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.