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.7.18 to 3.8.3

Octopus 3.8

Changes in 3.8

Improvements

Upgrading

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

Octopus 3.7

Changes in 3.7

New Features

Improvements

Upgrading

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

Release notes

These are the features and fixes you'll get by upgrading from 3.7.18 to 3.8.3.

Changes in Octopus Server 3.8.3

  • 2468 - Immediately return logs if an automatic Tentacle upgrade fails
  • 2811 - Add support for Nuget and Zip packages greater than 4Gb in size
  • 2905 - Deployment now fails when the type of a custom package deployment script (not one bundled inside the package) is not compatible with the target machine
  • 3029 - Show a confirmation dialog when deleting an environment if there are variables that are scoped just to that environment
  • 3089 - Correctly evaluate #{if Variable} substitutions if there is whitespace between the variable and the closing brace
  • 3104 - Fixed UI bug that was incorrectly showing the environment condition control on rolling steps.
  • 3108 - De-duplicate email lists provided to the email Step

Changes in Octopus Server 3.8.2

  • 2929 - Fixed validation on step deletion, so steps that are being used for Auto Release Creation or Release Numbering cannot be deleted
  • 3069 - Check all columns use default database collation before upgrading
  • 3084 - Fixed a bug where the NancyContext would not be disposed if the underlying HttpListenerRequest failed to close
  • 3085 - Try to log web request context when unhandled exceptions are thrown in the web server
  • 3097 - Fixed a bug where a SQL Database transaction was held open for the life of the Octopus Server which was a potential cause for tempdb growth
  • 3099 - Resolved issue where no tenants were available for deployment when tenant view permissions did not match tenant deploy permissions

Changes in Octopus Server 3.8.1

  • 2784 - Correctly populate Octopus.Deployment.PreviousSuccessful.Id when the previous deployment failed
  • 3028 - Tenant counter is now visible on the dashboard
  • 3049 - Created a set of system variables containing information about the last successfully installed package
  • 3073 - Fixed a regression with the console output for the show-configuration command
  • 3080 - Fixed timeout with health checks on tenanted machines

Changes in Octopus Server 3.8.0

  • 3013 - Fix for auto-deploy to be more inclusive of machines when dealing with deployment-blocked scenarios
  • 3077 - Fix Javascript issue breaking the rolling deployment step page.
  • 3061 - Server side package download is not stopped when the deployment is cancelled

Changes in Octopus Server 3.7.18

  • 3035 - Do not provide default values for certain connection string parameters if they have been specified in the connection string
  • 3068 - Disabled steps are now marked as skipped during deployment
  • 3070 - Fatal errors in during deployment now show more detail