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.17.14 to 4.0.2

Octopus 4.0

Changes in 4.0

New Features

Breaking Changes

Upgrading

This release contains a few post-install data fixes that may take some time (depending on the size of your DeploymentProcess and User tables), 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 4.0.

Octopus 3.17

Changes in 3.17

See our release blog post for more details.

New Features

Octopus 3.17 introduces first-class Java support so teams can start deploying their Java apps in a safe, repeatable and reliable way! This release includes support to deploy to Tomcat, RedHat JBOSS EAP and Wildfly application servers and the Octopus built-in repository can now manage Java packages like jar, war, ear and rar files.

Improvements

  • Swagger support for the Octopus API
  • Improved user administration and authentication performance

Breaking Changes

There are no breaking changes in this release.

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

Release notes

These are the features and fixes you'll get by upgrading from 3.17.14 to 4.0.2.

Changes in Octopus Server 4.0.2

  • 3907 - Improvements to guided failure and manual intervention experience
  • 3918 - Removed an error being recorded in auto deploy logs when machines do not match any project triggers
  • 3925 - Tenant, Team, Project, Role, amd Channel chips can now be removed if added to filters, deployments, subscription and notification configurations
  • 3926 - Certificate and Account step template parameters can be now used in steps

Changes in Octopus Server 4.0.1

  • 3920 - Deploy action no longer visible for users who lack the ability on project overview page
  • 3921 - Fix for audit filter buttons overlapping

Changes in Octopus Server 4.0.0

  • 2576 - Octopus UI shouldn't leak memory any more
  • 2606 - The variable editor has been overhauled
  • 2636 - The Wait for packages to be downloaded option only appears for steps ordered before a package step, and the checkbox now retains it's value
  • 2667 - Deploy release page now displays the version previously deployed for each selected environment and tenant
  • 2725 - Added an extra option to the run on option of a step to better differentiate steps that run on the server and those that run on the server on behalf of roles
  • 2729 - It is now easy to create deployments for all tenants which do not currently have the selected version deployed to the selected environment
  • 2739 - Collapsed the tenant tag filter section by default to declutter the UI
  • 2741 - Ctrl-F will now open the browser search function while editing a script
  • 2772 - We have improved the Project Overview when the Project uses multi-tenancy and multiple channels
  • 2773 - Saving and testing of azure accounts shows result more clearly
  • 2843 - The project overview version filter now allows filtering of releases created after the page was loaded
  • 2844 - Resolved issue where selecting both the tenant and a matching tenant-tag resulted in a mis-match
  • 2857 - We have added a gutter to the versions preview that explicitly shows what versions are included or excluded from Channel Version Rules designer
  • 2871 - Clarified what the Run default XML transforms checkbox does when setting up XML Configuration Transforms as part of your deployment process
  • 2973 - We fixed a problem where the introduction to Tenant Tag Sets wasn't displayed properly when hosting the Octopus Server in a virtual directory
  • 3010 - We have fixed a bug where the code editor would not allow you to scroll down to the very bottom in certain circumstances
  • 3012 - We fixed a bug with the Promote button so the options actually make sense for multi-tenanted projects
  • 3062 - We updated the Configuration > License page to show more information relevant to your current license, including usage counts so you know if you are reaching your license limits
  • 3103 - The environments on the Project Overview are now sorted by Lifecycle phase order, then by their order within each phase
  • 3107 - We fixed some noisy JavaScript errors which were appearing in the browser logs
  • 3115 - Updated project sidebar to make it clear when a project is disabled
  • 3170 - Tenant logos now size correctly in Internet Explorer
  • 3177 - The matching tenant count is now shown correctly when reopening the scope of a variable
  • 3217 - Deployment preview now shows which steps will run on a per-tenant basis
  • 3349 - The unsaved changes warning is no longer shown when a step with a run condition is viewed without being edited
  • 3358 - Breaking Change Auto deploy now always re-deploys the most recent successful deployment
  • 3368 - The project search and group filter now always appears on the dashboard
  • 3417 - Breaking Change We removed the Page.N entries from the Links list of collection responses from the REST API and replaced them with some alternatives
  • 3423 - Users can now create projects if they are only members of empty project groups
  • 3424 - Deprecated StepName property in Release.SelectedPackages has been deprecated (and will be removed in a future release) in favor of the new ActionName property
  • 3461 - Run on Failure steps now show on the task summary tab if it is executed
  • 3555 - The url in the address bar is now formatted correctly when the tenant tag filter is applied on the project overview page,
  • 3593 - We added a new Octopus Server command called ssl-certificate to bind an SSL/TLS certificate to an IP address/port
  • 3602 - Azure errors are now displayed at the top of the page when editing a Cloud Service step
  • 3611 - We changed the audit log so it shows the full date and time instead of a summary like 1 hour ago
  • 3619 - We fixed a bug in the Releases list where the Channel tags would fail to be displayed next to each release
  • 3647 - Breaking Change Removed unused properties from the BuiltInFeedStats API
  • 3648 - Clarified how the package retention settings work on the dialog
  • 3650 - Added an icon for Unhealthy Azure cloud services
  • 3655 - The target machines for a deployment are now shown per tenant and environment
  • 3658 - Removed ResourceCollection.IsStale
  • 3664 - On deployment creation, tenants that do not match the channel tenant tags can't be selected, and those channel tags are no longer pre-filled on the deployment
  • 3684 - We fixed a series of small bugs that would cause unexpected results when searching for Tenants
  • 3700 - We improved the user experience for editing sensitive variables for tenants
  • 3715 - We fixed several bugs with the Deployment preview and which deployment targets will be included in the deployment
  • 3716 - The machine edit page now makes it clearer that a machine will not be considered for a tenanted deployment if it is not allocated to any tenants
  • 3717 - Improved auto-deploy machine evaluation to prevent machines being missed due to timing issues
  • 3720 - Breaking Change Removed the /api/letsencryptconfiguration/disable API
  • 3747 - Breaking Change The get_octopusvariable bash function now returns an empty string if the variable does not exist
  • 3750 - The docker steps no longer disappear from the step list when the page is refreshed
  • 3753 - Fixed error that occurs when saving IIS related project steps that were created by earlier versions of Octopus
  • 3763 - The links to Accounts, Users and Proxies now show when you only have the relevant view permissions
  • 3772 - We overhauled the Deploy Release page to make it easier to use when deploying a release to multiple environments or multiple tenants
  • 3778 - The step names now appear correctly in Reorder Steps after removing the all steps from a parent step
  • 3783 - Multiple Exit full screen buttons are no longer shown when editing scripts
  • 3786 - Clarified how to exclude directories when purging a custom installation directory
  • 3794 - We fixed a bug which would incorrectly display the introduction to tenants in the Tenant list screen even if you already have tenants defined
  • 3795 - The variable editor no longer hides unscoped variables when a variable with the same name is scoped to the filter condition
  • 3803 - Breaking Change Authentication provider information is now treated as a resource and served through it's own API
  • 3810 - When cloning a project, you can now choose a different Lifecycle for the cloned project
  • 3825 - Improved Octopus ‘new release’ notifications for expired trial licenses
  • 3831 - Breaking Change Removed previously deprecated Octopus.Server.exe configure options --masterKey, --storageConnectionString and --webAuthenticationMode
  • 3832 - Breaking Change Octopus.Server.exe regenerate-certificate has been replaced with Octopus.Server.exe new-certificate
  • 3833 - Breaking Change The --thumbprint-only option has been removed from the Octopus.Server.exe show-thumbprint command since it is no longer needed
  • 3834 - Breaking Change The NancyCookie AuthCookieService.CreateAuthCookie() used by custom authentication providers has been replaced with NancyCookie[] AuthCookieService.CreateAuthCookies(). This will only impact customers who have written custom authentication providers
  • 3842 - Breaking Change Removed the SynchronizationStatus and IndexingStatus properties returned by the /api/serverstatus/nuget API
  • 3847 - Fixed a bug with the /api/releases/[ReleasesId]/deployments/preview/[EnvironmentId] API which resulted in steps that are scoped to tenants to be returned for un-tenanted deployments
  • 3861 - Breaking Change By default Octopus will only attempt to run a step on up to 10 deployment targets at the same time, instead of attempting to run on every matching deployment target simultaneously
  • 3883 - The package used by a Script Step can now be downloaded directly on the deployment target just like the package used by a Deploy Package Step
  • 3898 - Fixed a bug on the Project Overview screen which would result in an error if you filtered by tenants before filtering by a release
  • 3901 - Snapshotted variables referencing deleted resources will clearly state that the resource is missing from the scope, instead of just not showing it and causing errors downstream
  • 3916 - Root document in Octopus API returns now all links
  • 3917 - Made it easier to deploy a release to multiple environments or multiple tenants using the Octopus UI
  • 3938 - Breaking Change Octopus UI supports now only the latest versions of major web browsers: Internet Explorer 11, Edge, Firefox, Chrome and Safari.

Changes in Octopus Server 3.17.14

  • 3912 - Major improvements to migrator memory and speed performance
  • 3915 - Fixed a XSS vulnerability with the Step Template Name (CVE-2017-16801)