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 2019.2.8 to 2019.3.7
Octopus 2019.3
Highlights
Octopus Server 2019.3 LTS is a roll-up release of Octopus 2019.1 and Octopus 2019.2 and the headline feature is Spaces which enables teams to group projects, environments, tenants, step templates, and other resources into a Space. It also includes a large number of enhancements and bug fixes along with database performance and cloud dependency updates.
Read our blog post to learn more.
Breaking changes
This release includes numerous break changes from the introduction of Spaces. Refer to the Octopus Deploy 2019.1 release highlights for the full details.
Octopus 2019.2
Highlights
User Invitations into Space Teams
We have added the ability to invite new users into Teams that are owned by Spaces. Previously, new Users could only be invited into System-level Teams, but now Spaces and Space Managers can be self sufficient by inviting new Users without needing to ask a more privileged user to first invite the user into a System team.
Improved Date Display
We've done some renovations around how we handle and display dates. Now, we display dates in your local timezone where possible, and if that isn't possible, we include the timezone, so it's much easier to tell when something happened if you're in a distributed team or in a different timezone to your Octopus Server. Unfortunately, this has meant we've had to make some breaking changes, but we believe the impact will be low.
Breaking Changes
- The
LastSeen
property onoctopusservernodes/ping
now returns an ISO8601 date instead of a formatted string - The human-readable
Completed
date on aTask
is now formatted with a timezone - The human-readable
Published
date on aPackage
is now formatted with a timezone - The
Rank
,LastSeen
andIsOffline
properties have been removed from the/api/OctopusServerNodes/{id}
endpoint, and are now available from a new endpoint/api/OctopusServerNodes/summary
- The
EffectiveExpiryDate
on the/api/licenses/licenses-current-status
endpoint is now formatted with aDate
(yyyy-MM-dd) rather thanDateTimeOffset
data type. - The third party libraries we use to read certificates have been upgraded to newer versions which include tighter certificate verification. This may reject incorrectly formatted certificates.
- The
write-verbose
PowerShell Cmdlet now mimics native PowerShell behavior more closely -write-verbose "myvar = " $myvar
is no longer valid and will throw apositional parameter cannot be found
error. Please usewrite-verbose "myvar = $myvar"
instead.
Release notes
These are the features and fixes you'll get by upgrading from 2019.2.8 to 2019.3.7.
Changes in Octopus Server 2019.3.7
- 5737 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log
CVE-2019-14268
Changes in Octopus Server 2019.3.6
- 5453 - Introduced table caching of user details in server, to address performance issues
- 5627 - Fix for TypeError on certificate search, when certificate data was in an unexpected state
- 5633 - Further fixes for boolean handling in the Azure Resource Group template step UI
- 5670 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
- 5690 - Fix for Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables
- 5700 - Fix for Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
- 5702 - Fix for incorrectly migrated user roles that could not be saved due to validation error
Changes in Octopus Server 2019.3.5
- 5615 - More defensive error handling when docker acquisition fails
Changes in Octopus Server 2019.3.4
- 5553 - Improve Performance of Dashboard by indexing temp table
- 5565 - Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
- 5571 - Fixed bug that caused automatic release creation failures to return 400 and 500 on package push
- 5576 - Fixed high CPU usage on deployment task page
- 5580 - Resolved issue where certificates with private keys were being shown as not having a private key
Changes in Octopus Server 2019.3.3
- 5531 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined
Changes in Octopus Server 2019.3.2
- 5457 - Improved the speed of the automatic release creation after a package upload
- 5516 - Automatic Release Creation now creates releases after a step rename
- 5517 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
- 5433 - Update to Halibut to ignore unnecessary ACL failures that were causing deployments to fail
- 5529 - Fixed an access control bug where project scoping was not being applied for
VariableViewUnscoped
andVariableEditUnscoped
permissions (CVE-2019-11632)
Changes in Octopus Server 2019.3.1
- 5446 - Fix for users seeing a blank screen when they were set up with no permissions
- 5454 - Improved the performance the Projects API when many projects use features that are based on step names
- 5459 - Auto Release Creation and Scheduled Triggers can now create releases for projects using Step Templates that reference packages other than the one uploaded. Improved the speed of the Machine status triggered AutoDeploy
Changes in Octopus Server 2019.3.0
2019.3 LTS
Changes in Octopus Server 2019.2.8
- 3748 - Fix for editing a release with a package that doesn't match channel rules
- 5272 - Octopus Cloud
Octopus Manager
team doesn't have permissions to export users permission structure - 5404 - Fix for broken Project settings page if project was cloned from another project that's not available due to permission/deletion/migration
- 5422 - Made the getting started guidance available to hosted customers and space managers
- 5423 - Adding null checking around database upgrade script
- 5425 - Docker acquisition script moved from Server to Calamari