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.14.15926 to 3.15.0
Octopus 3.15
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
Editpermissions now automatically assignsViewpermissions. 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.Clientversion4.19.0contains API changes corresponding with the multi-tenant deployment participation change, a minor breaking change for anyone using theMultiTenantDeploymentModeonProjectresources 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.
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 configurecommand 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 --upgradecommand - 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.
Release notes
These are the features and fixes you'll get by upgrading from 3.14.15926 to 3.15.0.
Changes in Octopus Server 3.15.0
- 2722 - Enable untenanted projects to be deployed to tenanted deployment targets
- 3428 - Acquire package and retention policy steps now show step number and name in variables
- 3570 - Unscoped variables deleted when user doesn't have VariableViewUnscoped permission
- 3597 - Added support for managing the Portal SSL certificate using Let’s Encrypt
- 3598 - Resolved issue with Azure Service-Principal accounts not being available for selection as value of tenant variable template
- 3605 - The command-line interface for Octopus and Tentacle will now warn you if a service restart is required after certain configuration changes
- 3606 - Clean up corrupt entries in the events table left behind by a previously resolved issue
- 3609 - Migrator now maps TenantId when migrating Deployments
- 3610 - Improved command-line interface for Octopus and Tentacle
- 3612 - Prevent automatic Tentacle upgrades from restarting the host machine
- 3614 - Bugfix: Release filtered dashboard does not show environments that deployment can be progressed to
- 3620 - Certificates with long IDs can now be assigned as Tenant Variable values without throwing a
StringTooLongException
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