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.0.24 to 3.1.3

Octopus 3.1

Highlights and new Features of 3.1

  • Azure support revisited - blog post
  • TLS 1.2 (Requires Tentacle 3.1) - blog post
  • Reporting - blog post
  • Breaking change: Due to the dependency on .NET 4.5 Octopus Server and Tentacle 3.1 are no longer supported on Windows Server 2003 or Server 2008 SP1 - more information

Read the blog post for more details on the changes and features introduced in Octopus 3.1.

Upgrading Tentacles: You can upgrade to Octopus Server 3.1 without upgrading any Tentacles and get all of the new 3.1 deployment features because Calamari will continue to work on both Tentacle 3.0 and 3.1 - more information

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

Release notes

These are the features and fixes you'll get by upgrading from 3.0.24 to 3.1.3.

Changes in Octopus Server 3.1.3

  • 2013 - Prevent multiple Octopus installations from unintentionally exceeding license limits
  • 2014 - Manually entering schedule date now correctly schedules a deployment in IE11
  • 2016 - When adding roles to a team the Add button is now shown once a role is selected.
  • 2019 - Deletions from octo.exe or client now audited and will be displayed in the audit trail
  • 2029 - Database migrations will be applied to the correct schema
  • 2031 - Don't enforce that AccountId exists on cloud service step when migrating from 2.6
  • 2032 - Bring back support for config transform files in subfolders
  • 2033 - Selecting script syntax now selects the syntax you chose
  • 2037 - Only show machines that are part of the deployment in the package acquisition task log
  • 2043 - Update syntax higlighting mode for the script editor when the user changes script syntax

Changes in Octopus Server 3.1.2

  • 1582 - IIS bindings preserved (i.e. not removed and re-added) if no changes required.
  • 2020 - Now prevents creating a Machine with no Uri via the API and prevents server from crashing on startup if there are invalid Machines
  • 2021 - Allow the database upgrade script that added the DeployedBy column to be run multiple times as a workaround for some customers. Also increased the database operation timeout to the maximum to allow more time for these scripts to succeed.
  • 2022 - Fixed a typo in the Windows Service feature page

Changes in Octopus Server 3.1.1

  • 2005 - Resolved issue with PowerShell 2.0 and sensitive-variables
  • 2006 - Fixed issue with Azure process now allows a deployment with no machines targeted
  • 2012 - Account to target Environment restrictions now correctly allow Accounts to be used in deployments to "Any Environment", specified by leaving the Account Environments setting empty

Changes in Octopus Server 3.1.0

  • 1617 - Added reporting capability as per http://docs.octopusdeploy.com/display/OD/Reporting
  • 1801 - Limit the number of tasks that can be run in parallel per Octopus Server node (defaults to 5)
  • 1803 - Created specific Azure Step Types as per http://octopusdeploy.com/blog/azure-changes
  • 1843 - Added configuration section for managing Octopus Server High Availability nodes as per http://docs.octopusdeploy.com/display/OD/High+Availability
  • 1873 - Reduced the size of Calamari by splitting the Azure functionality into a separate Calamari.Azure package
  • 1884 - Tentacle Upgrades can now be performed using the UI like they were in Octopus 2
  • 1902 - Octopus Server and Tentacle now support TLS 1.2 which requires .NET 4.5
  • 1914 - Allow setting physical path when deploying Azure Web Apps allowing you to deploy to a subfolder of the web site.
  • 1925 - Tasks can be filtered by the Octopus Server node that is assigned to the task
  • 1926 - Active tasks on the Tasks page are now filtered by the task filters
  • 1928 - Added a url for load balancers that will return 200 when an Octopus Server node is not in maintenance mode
  • 1985 - Provide a configuration setting to allow Azure PowerShell module to be loaded from installed location, rather than the version packaged with Calamari.

Changes in Octopus Server 3.0.24

  • 1937 - Relax license enforcement
  • 1955 - Windows Service and IIS App Pool Custom Account Passwords are now treated correctly as Sensitive values by default.
  • 1984 - Custom Expressions now save correctly for Windows Service and IIS App Pool Custom Account Password values.
  • 1986 - Removed duplicate -variables argument from offline drop PowerShell script.
  • 1988 - The OfflineDrop .cmd file now executes the .ps1 file in the local folder instead of incorrectly targeting the path where the package was built.