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 4.0.11 to 4.1.10

Octopus 4.1

Changes in 4.1

See our release blog post for more details.

New Features

This December release of Octopus continues the support for Java that was introduced back in 3.17, with the ability to export certificates as Java KeyStores, as well as configuring certificates directly within existing Tomcat 7+, WildFly 10+ and Red Hat JBoss EAP 6+ application servers. This release also allows Maven repositories to be configured as external Octopus feeds, meaning Octopus can now consume Maven artifacts as part of a deployment.

Improvements

  • Maven repositories as external feeds
  • Deployment of Java keystores and configuration of certificates in WildFly, JBoss EAP and Tomcat
  • Directories for task logs, artifacts and the package repository are now store as relative paths

Breaking Changes

There are no breaking changes in this release.

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

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.

Release notes

These are the features and fixes you'll get by upgrading from 4.0.11 to 4.1.10.

Changes in Octopus Server 4.1.10

  • 2668 - The database upgrade now checks whether the licence would be non-compliant after upgrade and aborts the upgrade in order to prevent getting stuck with an expired licence and not being able to deploy
  • 3454 - Digitally signed Octo.exe and Octopus.Clients.dll so that AV respects it more
  • 3802 - Added support for passing password on the commandline to docker login
  • 3910 - Added option to filter by phase name in lifecycles page
  • 4040 - Minor breaking changes Project and tenant name cannot include unsupported file system characters
  • 4102 - Now we only test the connection to the master database when creating or deleting the Octopus database, which in turn fixes a problem we introduced in 4.1.0 with upgrading Octopus in certain situations
  • 4130 - PowerShell script parameters with a trailing slash no longer break script execution
  • 4155 - Fix a bug where metadata component in release version is not working with SemVer 2.0 template
  • 4162 - Added the ability to prevent package scripts from being run by specifying the Octopus.Action.Package.RunScripts variable and setting it to false
  • 4165 - We no longer attempt to deploy packages when acquisition fails
  • 4169 - Fix for deployment process screen where viewing email step that references a deleted team
  • 4171 - Don`t show username for external groups in teams area
  • 4174 - Dynamic package feeds now working again with channel rules
  • 4187 - Check for $JAVAHOME now uses [[ -n "${JAVAHOME}" ]] instead of -v to support older versions of bash

Changes in Octopus Server 4.1.9

  • 3827 - Fix a bug where tasks with manual intervention are listed as the queued behind tasks on Task page
  • 3913 - Increased number of possible PowerShell variables in scripts to maximum available
  • 3963 - Corrected the help message explaining what a valid version number looks like
  • 3990 - Increased contrast of form elements and content hierarchy
  • 4032 - Validate that environment and project ids exist when creating or modifying tenants
  • 4072 - Swagger documentation now works if Octopus is running in a virtual directory
  • 4085 - Improved the performance of the project Library Variable Sets page when there are many variable sets
  • 4087 - Fix a bug where task summary does not show on Task page when it is waiting for manual intervention
  • 4090 - Selecting a single date on the Audit page now shows the correct date range
  • 4146 - Prevented the filter panel from opening when you set a quick filter
  • 4161 - Improve performance of tenant variables when large number present
  • 4164 - UI data refresh is now triggered almost immediately after a tab becomes active again if it has been longer than the normal refresh interval; The refresh will also occur if the tab is in the background at a 12th the normal rate
  • 4167 - Fixed a security vulnerability where incorrectly configured user roles and teams would allow members of those teams to escalate their own permissions - Octopus now actively prevents any user from escalating their own effective set of permissions - CVE-2018-5706

Changes in Octopus Server 4.1.8

  • 3950 - Deployment page will now show the explanation for tenanted deployment if the channel has tenant restriction
  • 3951 - Deployment page now has the ability to deploy to all applicable tenants and skip those which already have the release as the current version for the environment
  • 4052 - Fixes for paging parameters in API link collections
  • 4101 - The full value is now displayed for variable template TextBox controls
  • 4103 - Default value on the multiline text variable template no longer overlays
  • 4112 - Make the following scenarios easier:
  • Deploying to all applicable tenants for the environment
  • Skipping those tenants which already have the release as the current version for the environment
  • 4116 - Added warning and error text hints to Checkboxes
  • 4129 - Channel rules testing no longer fails when feedId is a bounded value
  • 4136 - Logo missing on the previous step template version no longer prevents the current version from being saved
  • 4145 - Fix problem in Firefox where selects required two clicks
  • 4148 - Removed empty value warning/info icons from variable editor

Changes in Octopus Server 4.1.7

  • 3755 - Disabling a step no longer deletes the channel version rules for that step
  • 4092 - Fixed package selection in IE 11
  • 4100 - Create step template now renders the selection text

Changes in Octopus Server 4.1.6

  • 3724 - Azure account verification is now deferred until the step runs, which means output variables from earlier steps can be used to resolve the account
  • 3856 - Azure account verification is now deferred until the step runs, so that Cloud Region scoped variables can be used to resolve the account
  • 4109 - Variable filters are now persisted to the query string
  • 4110 - Enable long path support for the Migrator
  • 4111 - Add release notes to Releases page
  • 4113 - Fixed a bug where package versions would give an exception for a package with >2100 versions
  • 4115 - Fix a bug where Release page will crash if the package feed type is resolved from a scoped variable
  • 4121 - Packages with a + can now be deleted via the API
  • 4134 - Fixed potential scoping bypass when referencing Azure accounts (CVE-2018-4862)

Changes in Octopus Server 4.1.5

  • 4093 - Retries during SSH deployments will now re-attempt to establish the connection
  • 4094 - Rolling deployment window size can now be set using bound fields selector
  • 4096 - Healty Check step now shows the correct mandatory roles for execution plan
  • 4098 - Fixes for dashboard width and alignment issues
  • 4106 - Fixed an issue that caused deployments to disconnected SSH targets to run forever

Changes in Octopus Server 4.1.4

  • 3956 - Making variable groups and overflow actions clearer in the variable editor
  • 4022 - Do not collapse the lifecycle in Release page if there is pending interruption
  • 4058 - Machine events now include show/hide details
  • 4066 - Accessing phases containing Environments outside of logged in User's Team Scope not longer throws an exception
  • 4067 - Lifecycle automatic deployment logs can now be found in Configuration > Diagnostics > Auto Deploy Logs
  • 4068 - Lifecycle automatic deployments may now take up to 30 seconds to respond, instead of immediately
  • 4075 - Steps used in Automatic Release Creation can't be disabled anymore
  • 4077 - Show full channel name on releases list and deployment details pages
  • 4079 - Tenant Tag Sets and Tenants in Infrastructure Summary now show the correct deployment target counts
  • 4080 - Release filter doesn't truncate long release numbers any more
  • 4081 - Adding or removing a variable set from a project no longer removes script modules from the project
  • 4084 - Group by Channel in Project Overview screen no longer throws error
  • 4089 - Variables can now be inserted to bound text fields via the list picker
  • 4091 - Users can now see environments that are scoped at the team level
  • 4097 - Missing resource tooltip displays the correct resource id now
  • 4108 - Update to version 3.0.1 of the versioning library

Changes in Octopus Server 4.1.3

  • 3923 - HEAD http requests now return the correct status code instead of 500
  • 4019 - Release progression section now shows "Redeploy" and "Try Again" buttons against each environment
  • 4021 - Sort variable values predictably in the variable editor based on their scope, value and source
  • 4053 - /api/machines and /api/machines/all API endpoints now allows filtering by machine IDs by way of the querstring ids passed in as a comma-separated list of IDs or specified multiple times
  • 4056 - Fixed community step update process
  • 4057 - Only include IIS related information if we're running on Windows when using a custom installation directory and encounter an unauthorized access exception
  • 4062 - Updated versioning library
  • 4064 - Common Variables in v4 no longer shows Variable Sets with no templates
  • 4069 - The output of the show-configuration command now includes license details
  • 4071 - Provide a column specific error message if two projects with different names resolve to the same Slug during migration and failed on the unique constraint check
  • 4073 - Fixed security vulnerability in machine update process by checking that the user has access to all environments (CVE-2017-17665)

Changes in Octopus Server 4.1.2

  • 2448 - SSH Targets now support transferring data larger than 2GB
  • 4012 - Fixed a bug introduced in Octopus 3.17.8 that would cause the Octopus Server to crash if the SQL Server connection became unavailable for a period of time
  • 4025 - Better experience when changing variable type to certificate
  • 4039 - Fix for the DateRange component’s width calculations (causing wrapping of day-cells in Firefox)
  • 4043 - User password complexity enforcement in the API is now being applied correctly
  • 4045 - Environment names in v4 dashboard no longer overlap
  • 4050 - Guest user gets created/enabled correctly when the authentication provider is enabled/disabled via the API
  • 4051 - Resolved issue with incorrect password when downloading certificates
  • 4060 - New portal updated to not allow password change for service accounts or the Guest account

Changes in Octopus Server 4.1.1

  • 3892 - The timeout for subscription webhooks can now be configured
  • 3909 - Windows Service deployments now retry starting and stopping services
  • 4005 - Sorting environments will now be reflected immediately on previous screen when you perform save action
  • 4008 - Reducing excessive warnings in variable editor for empty value scenarios
  • 4014 - Any orphaned tenanted deployments will be cleaned up when you upgrade to this version of Octopus Server
  • 4028 - Fixed a bug where the cursor would jump to the end of an input while typing in the variable editor dialog
  • 4031 - The email priority can now be chosen for email steps and email subscriptions
  • 4036 - Fix for test permission exporting failing if the users teams had permissions restricted using empty groups
  • 4041 - Allow users to remove a variable set from a project within the variable set row
  • 4046 - Fixed a race condition that could cause the list of steps to exclude in a deployment to be empty
  • 4047 - Fix tenant chips are not showing correctly in deployment page preview section
  • 4048 - Fix regression where steps that should not be able to be excluded from a deployment could be excluded

Changes in Octopus Server 4.1.0

  • 3569 - Added event group MachineHealthChanged, replacing the event category of the same name
  • 3652 - Task log, package feed and artifacts folders are now shown in the show-configuration command and in the settings UI
  • 3846 - Task log, package feed and artifacts folders are stored as relative to the Home directory when they can be, to make moving the folder structure easier
  • 3943 - Add support for exporting certificates for Java app servers
  • 3944 - Add support for Maven repos as external feeds
  • 4023 - F# and ScriptCS support fixed in Azure script steps
  • 4030 - Fixed an API exception from occurring when a variable name was null
  • 4033 - Fix for audit screen’s default date range not including today
  • 4034 - Fix for maintenance mode banner’s transparency problems
  • 4035 - All SQL Server and Database management is now performed through a single component for consistency

Changes in Octopus Server 4.0.11

  • 3954 - Added the ability to resize columns in the variable editor
  • 4010 - Getting started no longer crashes Octopus if the first release is not on one of the first 5 created projects
  • 4015 - Introduce a delay between connection retries if the connection to the Tentacle is refused as the Tentacle might not be ready to accept connections just yet. Many thanks to @frese for the contribution!
  • 4016 - Updating project overview to include wildcard for finer-scoped EnvironmentView permissions
  • 4017 - Removed unnecessary word-breaking CSS that was causing the design to break in various scenarios
  • 4020 - Update the mouseover popup on scheduled tasks to display the precise scheduled time, and display the scheduled task time in the tasks table
  • 4024 - Added missing option for re-deploying already installed packages
  • 4026 - Fix for showing you an error when you have 2 certificates variables with same name and both are missing from the library