Compare releases
Compare releases and check for compatibility between your existing Octopus Server and new releases.
Release notes
These are the features and fixes you'll get by upgrading from 3.13.10 to 3.14.15926.
Changes in Octopus 3.14.15926
- 3520 - Advanced project settings are shown by default after a users first successful deployment
- 3558 - Added Support to override Azure Service Management (Storage) Endpoint Suffix
- 3575 - Tentacle will now ignore partially downloaded packages that are a result of network failure or deployment cancellation
- 3584 - Improved UI to make it clearer that steps run ‘on behalf’ of roles are optional
- 3601 - Cloud Service Storage account list handles Azure service management endpoint override correctly
- 3607 - Resolved an exception starting Octopus Server when the current node name contains certain characters
Changes in Octopus 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 Octopus 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 atake
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 Octopus 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 withOctopus.Server.exe
orTentacle.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
andOctopusAzureCloudServiceDeploymentUrl
output variables when the deployment is completed. Many thanks to @micsco for the contribution!
Changes in Octopus 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
Changes in Octopus 3.13.10
- 3493 - User onboarding progress bar no longer appears after upgrading from 3.3.27 or earlier
- 3531 - Performance improvements to the deployment manifest clean up queries
- 3542 - Show the custom installation directory purge exclusions section when the Purge setting is bound to a variable
- 3543 - Resolved error creating deployment when certificate step-template parameters not supplied