A modern version of Octopus Deploy is any version running on SQL Server. When Octopus Deploy was originally introduced, it ran on RavenDB. Octopus Deploy 3.x migrated from RavenDB to Microsoft SQL Server. This section contains guides to covering various use cases you might encounter when upgrading a modern version of Octopus Deploy.
Upgrade scenarios
The default upgrade scenario is an in-place upgrade. Thousands of customers upgrade every month without errors. However, no upgrade process is ever 100% error-free 100% of the time. The typical errors we see are:
- Compatibility Errors: Upgrading to a new version isn’t supported by a license limitation, host OS version deprecation, or SQL Server version deprecation.
- Hyper-specific use cases: Windows runs a specific version of Windows without a random patch of .NET Framework installed.
- Breaking changes introduced in the product: we do our best to minimize these, but they can happen. For example, Octopus Deploy 2019.1.0 introduced spaces and how teams and roles were assigned. Any API scripts manipulating teams had to be updated.
Please choose from one of five common upgrade scenarios:
- Upgrading minor and patch releases
- Upgrading major releases
- Upgrading from Octopus 4.x or 2018.x to latest version
- Upgrading from Octopus 3.x to latest version
- Upgrading host OS or .NET version
Mitigating risk
The best way to mitigate risk is to automate the upgrade and/or create a test instance. Automation ensures all steps, including backups, are followed for every upgrade. A test instance allows you to test out upgrades and new features without affecting your main instance. We also recommend performing a System Integrity Check on your live instance before attempting to upgrade. If the integrity check fails, please contact support with the raw output of the task, and we can get that fixed for you.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Wednesday, October 4, 2023