Compare releases

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.

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:

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.

Upgrading

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