Download the latest Octopus Deploy release

Octopus Deploy Release Notes

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.

Choose two versions to see what's new:

Major features

Changes in 3.14

New Features

We are excited to announce the Octopus Deploy plugin for Atlassian Bamboo continuous integration server.

This includes build tasks to make it easy to integrate your build and deployment pipelines.

  • Package applications for deployment
  • Push packages to Octopus
  • Create Octopus releases
  • Deploy Octopus releases


Breaking Changes

Octopus Tentacle 3.14.15: Octopus Tentacle 3.14.15 is not backwards compatible with Octopus Server versions less than 3.14.15. This has been fixed as of Octopus Tentacle 3.14.159.

Octopus Server configuration automation: If you are using scripts to automate your Octopus Server installation, please test these scripts with Octopus Server 3.14.x. We have made some changes to simplify configuration of your Octopus Server, but weren't able to maintain 100% backwards compatibility with some of the more obtuse scripts we tested. If you encounter any problems, please look at the scripts generated when you use the Octopus Server wizard.

SQL Database schema upgrades: It may also be worth noting we have adjusted the SQL database schema upgrades so they can be run at the time, and by a user account, which best suits your scenario:

  1. Automatically after the installer completes (new behaviour) - this runs the schema upgrades as the user account who started the installer - falls back to the existing behaviour if the installing user cannot access the SQL database
  2. Automatically during the Octopus Server startup (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
  3. Automatically when executing the Octopus.Server.exe configure command for a setting which is stored in the database (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
  4. Manually by executing the brand new Octopus.Server.exe database --upgrade command - this will run the schema upgrades as the user account who started the command

This may not affect many customers, but enables some advanced scenarios where you can grant limited privileges to the Octopus Server account, and grant schema change privileges to a special account used for installation.

SQL Error 4060 - Cannot open database "OctopusDeploy" requested by the login. The login failed.

If you see an error message like this after the installer completes, you can start the Octopus Server just like before and let it perform the schema upgrades.


Read the upgrade guide for more details on upgrading from your current version to Octopus 3.14.

Detailed release notes

Changes in 3.14.1592

  • 3586 - Tasks running on an HA node that fails to check in will be marked as failed
  • 3589 - Offline drops now detect if a sensitive variables file is available, and prompts for the password automatically
  • 3599 - Fixed a problem that would show an annoying error message when trying to upgrade from Octopus 2.6.5 to Octopus 3.14.x
  • 3600 - Fixed an issue introduced in 3.14.159 that caused prompted variable not to be set at deployment time

Changes in 3.14.159

  • 3330 - Improved the performance of the update variables process at the end of each deployment step
  • 3545 - Azure resource group deployment names are unique and less than 64 characters long
  • 3567 - Task log headers now indicate whether an action was run on behalf of a targer instead of on the target itself
  • 3572 - Most list api endpoints now support a take query parameter to control the page size, allowing more than 30 results to be returned at a time
  • 3577 - Azure Web App step correctly reloads the site list when editing
  • 3578 - Show additional configuration values on the Configuration -> Nodes -> Configuration Settings page
  • 3580 - User invitations can be used only once now
  • 3583 - Step Update works now when the update is performed while the template is being modified

Changes in 3.14.15

  • 3094 - Running a step template now populates its default parameter values
  • 3524 - Cloned projects now include the correct lifecycle
  • 3552 - OpenID Connect authentication provider now supports IPs that only use RSA keys
  • 3559 - A new HA node leader will be elected when there are only follower nodes
  • 3561 - Recover from hung state when IIS based deployments are cancelled
  • 3562 - All error messages are now written to stderr even if the --noconsolelogging switch is used with Octopus.Server.exe or Tentacle.exe
  • 3563 - Improved the master key validation we apply when connecting an Octopus Server instance to an existing database
  • 3565 - Octopus Server, as part of upgrading, now detects if the SQL Database schema upgrade can be performed before attempting them
  • 3566 - Fixed a problem where an audit event could be formatted incorrectly, causing the audit query to break
  • 3568 - Clarified that Roles group Permissions
  • 3574 - Add commands to create and backup certificates used by the Server for Tentacle communication
  • 3576 - Azure Cloud Service deployments will now set OctopusAzureCloudServiceDeploymentID and OctopusAzureCloudServiceDeploymentUrl output variables when the deployment is completed. Many thanks to @micsco for the contribution!

Changes in 3.14.1

  • 3459 - IIS application pools and websites can optionally be started as part of the deployment step
  • 3549 - Fix to the Certificate table to help avoid primary key violations
  • 3554 - Octopus Server and Tentacle will now be released on a separate cadence
  • 3147 - Improved the database schema upgrade experience