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.12.8 to 3.14.15926
Octopus 3.14
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
Improvements
- We've updated our ‘Deploy to IIS’ step to add support to control how your web sites and app pools are started after a successful. deployment. This is a great addition to one of most popular steps.
- Octopus is now generating all its certificates using using SHA256, instead of the older SHA1. We blogged about this previously when the SHAttered security vulnerability was announced and we've updated Octopus as promised.
- Octopus Server and Tentacle will now be released on a separate cadence. Tentacle will now be versioned/released independently and it will now come with its own release notes. This is a minor point but it should make it easier to upgrade Octopus going forward!
- Octopus Server database schema updates are now more transparent. Now when you upgrade Octopus to 3.14.0, or newer, the database schema upgrade will be performed immediately after the software upgrade, clearly showing the progress of the schema changes.
- We've added some new database indexes and we greatly reduced the memory usage on all HTTP requests. This means Octopus can spend less time cleaning up after itself, and more time being productive on your behalf.
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:
- 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
- Automatically during the Octopus Server startup (just like before) - this runs the schema upgrade as the user account who started the Octopus Server
- 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 - 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.
Upgrading
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.14.
Octopus 3.13
Changes in 3.13
New Features
We are excited to announce that Octopus now includes first-class support for Deploying Azure Service Fabric applications.
New deployment steps include:
- Deploying a Service Fabric App (learn more)
- Running a Service Fabric SDK PowerShell Script (learn more)
You can also read our guide on Continuous Integration for Service Fabric.
Improvements
- You can now enable HTTP Strict Transport Security (HSTS)
- You can now configure optional lifecycle phases
- We have improved browser caching of expensive operations like loading the dashboard
- The message on the deployment overview can now be customised, refer to failing a script with a message
- You can now edit the state of a task from the task screen by providing the new task state and the reason for the change.
- You can now configure channel-indexed version templates so you can use a consistent version scheme across channels
Breaking Changes
Please note there is a minor breaking change in this release around the show-configuration
command. This will only affect customers who use the show-configuration
command for things like automating Octopus Server installation and configuration.
Octopus.Storage.NodeName
has been corrected to be Octopus.Server.NodeName
.
See this GitHub Issue for more details.
Upgrading
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.13.
Octopus 3.12
Changes in 3.12
New Features
Improvements
Upgrading
Read the upgrade guide for more details on upgrading from your current version to Octopus 3.12.
Release notes
These are the features and fixes you'll get by upgrading from 3.12.8 to 3.14.15926.
Changes in Octopus Server 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 Server 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 Server 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 Server 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 Server 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 Server 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
Changes in Octopus Server 3.13.9
- 3433 - Improved Lifecycle API validation to ensure environments are valid
- 3449 - Only child steps can be moved into rolling deployments. Azure Resource Group steps can now be child steps as well
- 3473 - Azure Resource Group deployments now generate unique deployment names
- 3519 - Bugfix allowing blocked deployments to continue phase progression
- 3529 - Fixed error 65532 when running Tentacle upgrades on PowerShell v2
- 3530 - You can now upgrade the database schema using the
Octopus.Server.exe database --upgrade
command - 3534 - Fixed orphaned tenanted deployment integrity check - now it ignores un-tenanted deployments from the test
- 3536 - Improved performance of writing task logs by about 10%
- 3537 - Fixed a JavaScript problem with the Azure Service Fabric step's hamburger menu
- 3539 - Improved performance for each HTTP request by reducing memory allocations
Changes in Octopus Server 3.13.8
- 2943 - Allow some files to be retained when purging a custom installation directory
- 3048 - Selecting release on multi-tenant project dashboard will now update the dashboard
- 3101 - Tenanted deployments are now cascade deleted when the tenant is deleted
- 3210 - Errors when applying retention-policy on deployments targets now treated as warnings, and will not fail the deployment
- 3249 - Resolved issues with filtering tenants list in portal
- 3347 - Log relevant error message if trying to import certificate into Root store for user
- 3401 - "Document type" added as filter for audit log and subscriptions
- 3402 - Improved description of the permissions table on the permission test page
- 3479 - Added a link to help for dynamic package feeds
- 3496 - We now explicitly mention that IIS step supports Websites, Web Applications and Virtual Directories
- 3504 - Add the ability to export the audit log as a CSV file
- 3508 - 'Send an Email' step summary shows now only teams selected by the user
- 3510 - We now explicitly tell the user that release deletion will remove deployments from all dashboards
- 3514 - Fix Lifecycle
required to progress
details not saving correctly - 3516 - Made it easier to see the options to upload packages to the built-in package repository
- 3528 - Ensuring a channel belongs to a project upon release creation is now case insensitive
Changes in Octopus Server 3.13.7
Changes in Octopus Server 3.13.6
Changes in Octopus Server 3.13.5
- 3498 - Resolved error when deploying old versions of step templates introduced in 3.13.4
- 3286 - Editing ‘environment scoped’ variables in a variable set no longer needs
EnvironmentEdit
permission - 3357 - Enabled certificate parameters to step templates
- 3396 - Removed broken 'Create variable' link from certificate step template parameters
- 3414 - Only remove SSL certitificate from the website that the
HTTPS
binding is removed from - 3467 - Auto deploy will no longer attempt deployment to machines without roles relevant to the deployment
- 3478 - Error reason will be shown when license signature could not be verified
- 3480 - Health checks now log any machines that could not be checked because of tenant permission restrictions
- 3484 - Variables with colons can now be used as Web Site and App Pool names
- 3485 - 0 will no longer be repeatedly written to deployment logs for IIS deployments
- 3486 - Fixed typo in the scheduled task tip
- 3490 - Fixed a performance problem where both an unbounded and paginated SQL query were issued for some requests
- 3492 - Fixed a Service Fabric upgrade bug where we were using an incorrect argument
Changes in Octopus Server 3.13.3
Changes in Octopus Server 3.13.2
Changes in Octopus Server 3.13.1
- 2551 - Fixed a race condition that caused re-packing of deployments to fail (eg Azure deployments)
- 3411 - Improved validation around IIS deployment step variables
- 3464 - Package transfers will no longer appear to be in progress if a task fails or is canceled
- 3465 - Package transfers from Octopus to Tentacle no longer retry when the task is canceled
- 3466 - Tentacle can now bypass the proxy when registering as a polling tentacle
Changes in Octopus Server 3.13.0
- 2380 - Added ability to override a task status
- 2630 - Adding verbose logging around Azure module logs
- 3293 - Deploy a cluster application for Service Fabric
- 3294 - Run adhoc PowerShell scripts for Service Fabric
- 3295 - Support Client Certificates as a security mode for Service Fabric
- 3296 - Support Azure AD as a security mode for Service Fabric
- 3297 - Automated application versioning for Service Fabric
- 3298 - On-prem support added for Service Fabric
- 3389 - Improve performance of dashboard by leveraging browser caching
- 3400 - Avoid refreshing dashboard page if window is not visible
- 3442 - Reference versions from other channels in Release Version Template
- 3444 - Add missing property
Octopus.Communications.WebSocketPrefix
to output ofshow-configuration
command - 3445 - Breaking change: Corrected
Octopus.Storage.NodeName
property inshow-configuration
output to beOctopus.Server.NodeName
- 3453 - Regression in license limiting for special licenses
- 3457 - IE9 and IE10 users are warned that their browsers won't be supported in Octopus 4
Changes in Octopus Server 3.12.9
- 3185 - Excluding a machine from a deployment will no longer exclude that machine from a subsequent auto-deploy of the same deployment
- 3418 - Audit messages now record extra details (differences) when documents are created and deleted
- 3452 - Fix not being able to add more than one environment to a machine at a time
- 3455 - Tenant count is now displayed correctly on the main dashboard
Changes in Octopus Server 3.12.8
- 3380 - The message on the deployment overview can now be customised, refer to failing a script with a message
- 3399 - Prevented missing indexed variable from causing a stack overflow
- 3415 - Support Optional Lifecycles
- 3426 - Sign Calamari.exe and Calamari.Azure.exe
- 3440 - Fixed a race condition in sensitive variable masking that caused the process to crash