Compare releases

Compare releases

Find out what's new in the latest Octopus Deploy release, or compare the latest release to what you're currently running to see what's changed.


These are the most important features you'll get by upgrading from 2018.10.7 to 2019.3.3

Octopus 2018.11


This release is our first fast lane release after the 2018.10 LTS release with long term support. If you're not sure what this means to you, please read the announcement to help decide which lane works best for you.

Even though it's been released at the start of January 2019, its a wrap up of all the work we did at the end of 2018. It mainly contains UI updates, but also a bunch of important fixes.

Cloud Dependency Updates

All the Cloud dependencies that ship with Octopus have had an update:

  • Azure PowerShell modules upgraded to 6.11.0 (Requires PowerShell 5.1)
  • Azure CLI upgraded to 2.0.50
  • AWS PowerShell modules upgraded to 3.3.390.0
  • AWS CLI upgraded to 1.16.52
  • Terraform CLI upgraded to 0.11.10
  • Terraform AzureRm plugin upgraded to 1.19.0
  • Terraform AWS plugin upgraded to 1.51.0
  • Terraform Azure plugin upgraded to 0.1.1

Database performance updates

At the end of the installation process, Octopus will rebuild or reorganize database indexes that are fragmented to ensure the database performs at its best. This may take some time, depending on the size of your database.

As normal, all of the usual steps for upgrading Octopus Deploy apply.

Octopus 2018.12

This release consists of a few important bug fixes and enhancements. Most notable is updating our Azure support to handle deprecated management certificate better.

Octopus 2019.1



To bring in the new year, we are shipping our latest feature. Spaces is a comprehensive set of user interface, API and permission system changes designed to make it easier to configure deployments in busy organizations.

From our documentation:

Spaces let you partition your Octopus server so that different teams can only access the projects, environments, and infrastructure they work with from the spaces they are members of.

Teams & Permissions

We have re-designed the way permissions are assigned to Teams, making it easier than ever to configure and manage permissions for your users. As part of this we have rewritten much of the code that enforces these permissions so that we can make sure Octopus keeps your data safe. There are a few breaking changes involved here, so customers with complex permission configurations may want to pay careful attention to the release notes.

Breaking Changes

Before upgrading to this release, there are some breaking changes in behaviour that you need to be aware of.


Some tentacle operations now necessarily act within a space and the CLI commands accept an optional spaceName parameter. These commands are the register-with, register-worker, deregister-from, deregister-worker and show-configuration commands. Since the deregister-* commands act within a single space, and a single Tentacle can register machines in multiple spaces, these commands no longer remove trust for the Octopus Server. To remove trust, the command Tentacle.exe configure --remove-trust=... must instead be used.

API Changes

A number of API route changes were made in this release. Most routes now include a segment that represents the target Space. We provide a Default Space for backwards compatibility with the old routes.

Disabling the Default Space will turn off backwards compatibility. Anything that leans on the old API routes, integrations, extensions and tools may break when the default spaces is disabled. More information here

Many of these changes are also reflected in Octopus.Client, so it is recommended your integrations update to the latest version of Octopus.Client (at least 5.0.0).


The property representing whether multi-tenancy was enabled is no longer exposed through the features endpoint (/api/featuresconfiguration) but is now exposed through the tenancy status endpoint (/api/tenants/status or /api/{spaceId}/tenants/status).

Built in Repository & Feeds

The endpoint responsible for fetching and configuring settings related to the built in package repository (/api/repository/configuration) has been removed. Instead, the built in package repository settings are managed the same way as other feed types, through the feeds api (/api/feeds/{feedId}), where the {feedId} is the Id of the built in package repository. The built in package repository endpoint has moved from /api/serverstatus/nuget to /api/feeds/stats or /api/{spaceId}/feeds/stats

ServerTask links

The Links collection on Tasks (TaskResource) no longer contains Artifacts and Interruptions links for the subset of task types for which they do not apply (i.e. “System” tasks).


UserRoles (UserRoleResource) used to contain a single collection of GrantedPermissions, but now instead contains separate collections for permissions that apply within a space (GrantedSpacePermissions), and permissions that apply at the system level (GrantedSystemPermissions). Similarly, PermissionDescriptions has been replaced by SpacePermissionDescriptions and SystemPermissionDescriptions


Teams no longer contain scope properties (ProjectGroups, Projects, Environments and Tenants), nor do they reference UserRole. These concepts have been replaced by the new entity type ScopedUserRole.


This new entity type exists at /api/scopeduserroles. It represents an application of a UserRole to a Team. It also includes the scope properties (ProjectGroups, Project, Environment and Tenants) that apply for that UserRole. This enables UserRoles with different scoped applied to the same Team (i.e. the same group of Users), and also allows the same Team to have access to different Spaces.


Artifacts (Artifactresource) no longer contains RelatedDocumentIds. Instead there is a new property called ServerTaskId to indicate which ServerTask the Artifact was collected from. Artifacts can only be associated with AdHoc Script tasks and Deployment tasks.

Permission changes

The implementation of our permissions system was changed in order to support Spaces. At the same time, we took the opportunity to apply permissions more consistently, so that we could reduce confusion while also making things more secure.

This resulted in some breaking changes to permissions where the old system was not consistent. In most cases, the new system is more restrictive than the old system, so upon upgrade most users should not have more access than they previously had.

Some of these changes require additional permissions to do certain tasks. For users that tend to use built in User Roles, Octopus should continue to behave as it did before and no action is required.

Customers with complex permission configurations may want to pay careful attention to the release notes, as there may be action required after upgrade. While most of these changes affect edge cases that normal users won’t encounter, we recommend testing your permissions after upgrade to ensure they behave as you intend.

In general *Edit and *Delete permissions, now strictly requires the corresponding *View permission.

For example: AccountDelete now also requires AccountView MachinePolicyEdit now also requires MachinePolicyView And so on


Retrieving accounts by ID is more restrictive now (to be consistent with the Index endpoint). It used to allow you to see documents with partial scoping (eg. no tenants) when your permissions were scoped, which is no longer the case. Getting the usage of accounts may require ProjectView


Retrieving certificates by ID is more restrictive now (to be consistent with the Index endpoint). It used to allow you to see documents with partial scoping (eg. no tenants) when your permissions were scoped, which is no longer the case. Getting the usage of certificates may require ProjectView Viewing the public Octopus Server certificate no longer requires the MachineEdit permission. It is accessible by any authenticated user.

Action Templates

Search and logo retrieval requires ActionTemplateView Get usages of the action template requires ProjectView Updating deployment actions will skip actions that are inaccessible rather than failing Updating deployment actions additionally requires the ProjectView permission


Users with could not view/edit or create a completely unscoped artifact if their permissions were scoped, but now they can.


AuditView permission has been removed because it is no longer applicable, as you always needed EventView to actually see events via the Audit screen. There is no migration required for this, e.g. if you had AuditView without EventView previously, then you could not see any events anyway.

Cloud Template

The cloud template endpoint no longer requires the ProcessEdit permission. It is accessible by any authenticated user.


Creating a deployment additionally requires ReleaseView, ProcessView, ProjectView, EnvironmentView, DeploymentView Modifying a deployment additionally requires EnvironmentView Tenanted deployments additionally require TenantView

Deployment Process

Getting a template requires ReleaseView Getting a list of Deployment processes now requires ProcessView


Events that are scoped to multiple of the same type of document, and your EventView permission are scoped to the same documents then you can now see that event. You can see events that partially match your permissions scopes, instead of needing to match all of your permission scopes.


Downloading packages or viewing the delta signature for the built in feed additionally requires the FeedView permission Searching for packages in the built in release feed requires ReleaseView and ProjectView. Modifying configuration for the built in feed now requires the BuiltInFeedAdminister instead of the ConfigureServer permission.


InterruptionViewSubmitResponsible is the only permission required to take responsibility and submit and interruption when that interruption has assigned responsible teams. To view an assigned interruption you may require UserView

Library Variable Sets

LibraryVariableSetView is now consistently checked in all scenarios where a variable set is accessed.


Lifecycles can be created or edited only when the user has EnvironmentView access to all environments used by that lifecycle EnvironmentView is required to preview a lifecycle ‘ProcessView’ and ‘ProjectView’ are required to view projects connected to a lifecycle The lifecycle progression API now requires ProcessView, DeploymentView, TenantView, EnvironmentView and LifecycleView

Projects & Project Groups

Creating a project group and adding a project no longer requires ProcessView


When replacing an existing package, the BuiltInFeedPush permission check will take into account the project scopes applied to that permission You can no longer get the delta signature of a package scoped to a project, while your BuiltInFeedDownload permission was scoped to a different project


Editing a release requires ProcessView and ProjectView Updating release variables requires ProjectView Viewing a release requires ProjectView Getting a release template requires ProcessView and LifecycleView Getting the release progression requires ProcessView and LifecycleView

Server Nodes

Octopus Server Nodes GET endpoints are accessible to authenticated users - they don’t require administrator access. Any modifications still required administrator access.


Cancelling a task requires TaskView, and any permissions that would be required to create that type of task (for example, EnvironmentView or MachineEdit for AdHoc Script tasks) Re-running a task requires the same permissions as creating that task. You can now always view the raw task log if you have TaskView for that task and also TaskViewLog. Modifying a task’s state when that task is not a Deployment task now requires TaskEdit scoped to that task, instead of requiring unscoped TaskEdit


Getting tenant variables requires ProjectView Getting missing variables for tenants requires LibraryVariableSetView Updating the sort order for tag sets requires TagSetEdit instead of TenantEdit


Getting a list of users will always return at least one result (yourself), even if you lack the UserView permission

Octopus 2019.2


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 on octopusservernodes/ping now returns an ISO8601 date instead of a formatted string
  • The human-readable Completed date on a Task is now formatted with a timezone
  • The human-readable Published date on a Package is now formatted with a timezone
  • The Rank, LastSeen and IsOffline 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 a Date (yyyy-MM-dd) rather than DateTimeOffset 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 a positional parameter cannot be found error. Please use write-verbose "myvar = $myvar" instead.

Octopus 2019.3


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.


Changes in Octopus 2018.10.7

  • 5433 - Update to Halibut to ignore unnecessary ACL failures that were causing deployments to fail

Changes in Octopus 2018.10.8

  • 5552 - Improve Performance of Dashboard by indexing temp table
  • 5758 - Updating no-javascript link to https

Changes in Octopus 2018.10.9

  • 5758 - Updating no-javascript link to https

Changes in Octopus 2018.11.0

  • 5128 - Provide support for --tiller-namespace, --tiller-connection-timeout and --timeout on helm upgrade command
  • 5134 - Added --user as an alias for --username to the command line interface
  • 5138 - Improved how the task log is displayed, most notably when conditions are used and in failure scenarios
  • 5162 - Added an overflow menu to the step edit page to delete and enable/disable the step
  • 5168 - Corrected the order of Tenant Tags in the summary text for step conditions to match the order defined on the Tenant Tag Set
  • 5169 - Updated the task list task type filter to support the full range of task types
  • 5172 - Improved the UI layout for checkbox validation messages and fixed overlapping validation and actions on tenant variables
  • 5176 - Flag HA server node as offline when shutting down
  • 5178 - Fixed an issue that prevented script types other than PowerShell from running during Azure steps
  • 5180 - Okta authentication provider now allows override of the claim used to determine the user's username
  • 5181 - Fragmented database indexes are automatically rebuilt or reorganized after other upgrade script have run
  • 5182 - Included a link to the project group on the project edit screen
  • 5183 - Added code folding support to the code editor
  • 5184 - Task re-run permission corrected in user interface, now operates same as the original adhoc-task run
  • 5185 - Cloned K8S deployment steps no longer delete K8S resources deployed by other projects
  • 5186 - Fixed an issue where the incorrect radio button for certificates on a HTTPS binding was selected by default
  • 5188 - Remove ability to use old (pre 4.0) portal
  • 5189 - Added missing validation for packages to the Deploy to NGINX step
  • 5190 - UI fix for variable editor popover menus being visually cut off
  • 5193 - Updated a number of dev dependencies and run-time dependencies including moment and lodash
  • 5012 - Updated Web App deployments to use XML publish endpoint enabling deployments for Linux based Web Apps using web deploy

Changes in Octopus 2018.11.1

  • 5194 - UI wording updates to SSH target and .NET framework options
  • 5195 - Fixed a bug where deleting an unsaved step from the overflow menu would delete the last step in the deployment process instead

Changes in Octopus 2018.11.2

  • 4891 - Fix an issue meaning Infrastructure tab didn't load correctly for some permission scoping combinations
  • 4929 - TLS certificates can now be configured on Kubernetes Ingress
  • 5118 - Resolved issue preventing Kubernetes custom resource YAML containing variable expression from being saved
  • 5146 - Bugfix: Support additional values file sourced from helm chart package
  • 5177 - Fix and issue where deployments to cloud services would fail to authenticate after migrating from old versions of octopus
  • 5179 - Squashed bug resulting from removing package references from cloned steps
  • 5199 - Made the capitalization of headings on the project settings page consistent
  • 5200 - Fixed an issue on slow connections where attempting to edit a newly cloned step caused a page refresh rather than navigating to the edit step page
  • 5201 - Made the Machine Policy field on a new deployment target always visible to reduce confusion
  • 5202 - Kubernetes Service fields now displayed before Ingress fields on Deploy Kubernetes Containers step
  • 5203 - Ensure K8S lifecycle hooks encode each command line as a string
  • 5209 - Fixed an issue preventing new steps from being added and or modified when a step uses an account variable selector such as AWS and Terraform steps
  • 5212 - Fix grammar in the summary text for a child step when used in a rolling deployment

Changes in Octopus 2018.11.3

  • 5210 - Resolved JSON encoding issue with k8s config maps and secrets
  • 5215 - Improved handling of transient I/O errors when writing server logs
  • 5217 - Steps can now be cloned to a different project
  • 5218 - Fix for resource searching that incorrectly escaped left square brace, resulting in incomplete query results
  • 5221 - Downgraded Octopus.Dependencies.AzureCmdlets to v6.8.1

Changes in Octopus 2018.12.0

  • 5045 - Reduced the key size of the index IXServerTask_Common so it no longer exceeds the maximum key size
  • 5205 - Upgrade to latest version of Azure libraries in Octopus Server means breaking some management certificate support
  • 5216 - Turn off context autosave in AzureRM powershell scripts
  • 5219 - Allow step templates to be created from a step
  • 5222 - Server can now download all NuGet packages created with the latest version of NuGet
  • 5227 - Bugfix - Referencing PackageVersion variable from another step is not evaluating correctly
  • 4287 - Fix for TaskView check incorrectly operating on health check tasks when scoped.

Changes in Octopus 2018.12.1

  • 2521 - Polling Tentacle timeout can now be configured via the machine policy, replacing the Octopus.Server.exe.config settings. If you are using those settings, open each machine policy, check the settings and save the policy
  • 5124 - Added support for touch screens when reordering lists (e.g. when re-ordering steps)
  • 5174 - Attempt to cancel any running tasks when shutting down the Octopus service
  • 5204 - SSH and Tentacle connection timeouts and limits can now be configured via the machine policy
  • 5229 - External feed URLs are now trimmed to prevent validation errors
  • 5231 - Squashed null reference error in Deploy Kubernetes Containers step when secret has no data
  • 5233 - Added support for AWS S3 and CloudFormation steps to run on ssh Linux targets
  • 5237 - Fix for incorrect permission warning on Project overview screen if user only had ProjectView scoped on group dimension

Changes in Octopus 2019.1.0

  • 5226 - Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
  • 6084 - Breaking change TeamResource structure change - improved scoping ability per team
  • 5239 - Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server
  • 3055 - Fix for inconsistencies in EventView permission calculations.
  • 4362 - Tentacle Manager no longer overwrites Tentacle instances with the same name.
  • 4831 - Tentacle Manager now properly handles selecting and creating of Roles that include spaces

Changes in Octopus 2019.1.1

  • 4562 - Added option to exclude unhealthy targets at the beginning of a deployment
  • 5141 - Allow overriding namespace in Helm Upgrade step
  • 5234 - Added Python 3 support for script steps, ad-hoc scripts and custom deployment scripts
  • 5238 - Steps that are skipped due to not finding any deployment targets to run on are now marked as skipped rather than successful, resolving an issue where the incorrect run time was shown
  • 5240 - UI fix for package version rendering issues on Create Release screen
  • 5241 - Octopus.Migrator.exe now uses the ID to name exported certificate files to ensure all certifcates are exported correctly, even superseded certificates
  • 5244 - New-OctopusAzureWebAppTarget command slot name parameter is now honoured
  • 5245 - Variable expressions that reference a non existent JSON property now evaluate to an empty string
  • 5248 - The server now completes it startup sequence before processing a shutdown request
  • 5249 - Fix for a user with Tenant scoped ProcessEdit would prevent UI from showing Create Release action
  • 5250 - Fix for ProcessEdit permission correctly operating with Tenant dimension to show add channel button
  • 5251 - Fix for ProjectEdit permission correctly operating with Project Group dimension to allow settings editing and tenant linking
  • 5252 - Fix to ensure post installation scripts correctly refresh views

Changes in Octopus 2019.1.2

  • 5247 - Fixed a bug where the Feeds endpoints would not return a backwards compatible FeedResource for old versions of octo.exe
  • 5253 - AWS now correctly uses the EC2 instance role metadata
  • 5254 - Package upload dates are now shown again (when available) on the previous versions dialog
  • 5255 - The refresh feed list button on the Run a Helm Update step no longer crashes
  • 5256 - Stopped showing the (unsupported) built in feed for the Run a Helm Update step
  • 5257 - Fix for permission error on Releases screen when user had valid Tenant scoped ReleaseView and ProcessView permissions

Changes in Octopus 2019.1.3

  • 5258 - Fix for update deployment process returning incorrect error for missing ProcessEdit permission when it's Tenant scoped
  • 5259 - Resolved migrator issue where attachments were causing '$' to be left in IDs
  • 5260 - Fix for Tenant scoped ProcessEdit permission warning when updating Action Templates
  • 5262 - Fixes errors during upgrade for instances that cannot access the package roots parent directory

Changes in Octopus 2019.1.4

  • 5266 - Fixed error when health checking Tenant scoped targets in 2019.1.0 and later
  • 5268 - Fixed UI bug with exclude unhealthy targets setting

Changes in Octopus 2019.1.5

  • 5267 - Resolved error when cloning a channel-scoped step to another project
  • 5273 - Fix a bug when navigating to a community action template
  • 5275 - Fix for scheduled deployments that contain a deploy a release step failing with a permission exception

Changes in Octopus 2019.1.6

  • 3198 - Added support for variable substitution in ARM templates for complex types including array types
  • 4469 - Links in AWS error messages are now rendered as proper links
  • 4618 - Better error handling for Azure steps that display information from Azure
  • 5207 - Prevented infinite polling loop when navigation happens while request is in flight
  • 5243 - Add CAPABILITYAUTOEXPAND to CloudFormation step and ability to choose multiple IAM capabilities
  • 5265 - The correct artifacts now show on the release screen, fixing a bug introduced in 2019.1.0
  • 5269 - Fixed a bug where members of teams with no permissions could not assign interruption to themselves, even if that team was designated the responsible team for the interruption
  • 5271 - Fix an issue where deleting a CloudFormation stack would not wait until completion
  • 5278 - Allow ingress rules to be reordered
  • 5279 - Support Downward API for environment variables in Deploy Kubernetes Containers step
  • 5282 - Create release via Client API now works for .net standard
  • 5283 - Fix for Task screen incorrectly reporting lack of TaskView permission when it was granted only at the Space level
  • 5284 - Fixed various issues around permissions that allows access to projects through connected tenants

Changes in Octopus 2019.1.9

  • 4515 - Certificate filter doesn't work when there is more than 1 page or results
  • 5307 - Run Condition and Start Trigger sections no longer disappear when a validation error happens when saving a step
  • 5308 - Fix for audit screen and audit shortcuts reporting incorrect lack of permission for users who have EventView scoped
  • 5309 - Expose the K8S Pod termination grace period field
  • 5310 - Allow K8S TLS certificate to be empty
  • 5316 - UI fixing route issues that were causing pages to re-render when filtering
  • 5317 - Fix for server startup error (Error converting value “TaskViewLog”)
  • 5319 - Can't save previously created K8S container definitions

Changes in 2019.1.8 (release was disabled/hidden due to a bug found)

  • 4392 - Fixed the variable preview grid to expand columns to all available space
  • 5295 - Prevent SQL timeouts for auto-deploy triggers
  • 5298 - Fixed "Unbound variable" error when using set_octopusvariable with set -euo pipefail
  • 5305 - Rename "machine name" field on deployment targets to "display name"
  • 5306 - Show type (Polling Tentacle/Listening Tentacle/Cloud Region/etc) when viewing a deployment target
  • 5311 - Removed extraneous slashes in placeholder text for offline drop targets
  • 5313 - Outdated OctopusClient warnings now include user and agent type
  • 5315 - Save terraform sensitive values as Octopus sensitive values (CVE-2019-8944)
  • 4873 - Fix an escaping issue causing Authentication issues with Azure CLI when an Azure Service Principal Account key contains special characters such as those generated by the new Azure App registrations preview blade.

Changes in 2019.1.7 (release was disabled/hidden due to a bug found)

  • 5261 - Fix for Tenant scoped users who were incorrectly blocked from exporting certificates
  • 5280 - "Deploy a Release" steps now collect output variables from failed child deployments
  • 5289 - Fixed a bug where Project Viewers could not assign and submit interruptions
  • 5290 - Fixed error "This SqlTransaction has completed; it is no longer usable"
  • 5291 - Added warning logs for situations where an IIS web site deployment will fail to start the web site
  • 5293 - The built-in repository settings are now retained correctly when upgrading from versions prior to 2019.1.x
  • 5294 - Fixed a bug where Packages could be cleaned up by retention policies while still in use by Releases
  • 5296 - No longer leaving orphaned DeploymentActionId when deleting a step as part of deleting a channel
  • 5297 - Resolved performance problem writing to log files introduced in 2019.1.2
  • 5304 - Breaking change Removed the TaskViewLog permission. Any user that has been granted access to a Task through the TaskView permission can also view that Task's logs

Changes in Octopus 2019.1.10

  • 4384 - Fix for error in Variable Preview when a Tenant is connected to multiple environments
  • 4396 - Render Subject Alternate Names on certificates correctly
  • 4864 - Octopus instance management no longer relies on the Windows registry
  • 5150 - Added validation to make sure releases cannot be created without version numbers for all packages
  • 5299 - Fixed an issue where ACR as a docker feed would not resolve to the latest version when the number of tags exceed the default page limit
  • 5302 - Fix an issue where S3 step would not properly set special headers such as Cache-Control when provided as metadata
  • 5318 - Fixed bad link on Web Request Proxy settings page
  • 5321 - Improved validation messages for creating an SSH Connection target
  • 5323 - Fix an issue with S3 where the file metadata would not be updated if file contents did not change
  • 5324 - Resolved a High CPU issues triggered by retrieving package notes
  • 5326 - Incorrect load more and search inside Library Variable Sets and Script Modules
  • 5330 - Add additional logging when a K8S deployment fails

Changes in Octopus 2019.1.11

  • 5332 - Fix for release promotion being blocked when user could not see complete set of environments that are part of the phases
  • 5334 - JSON formatted output broken by non-formatted message
  • 5286 - Windows service state can now be specifically defined

Changes in Octopus 2019.2.1

  • 4897 - Add validation for drop down options for variable templates of type "select"
  • 5303 - 2100 SQL parameter limit hit when updating usages of step templates fixed
  • 5325 - Fixed the api/reporting/deployments/xml endpoint, a bug introduced in 2019.1.0
  • 5338 - Corrupt builtinrepositoryconfigurations-single configuration json column fixed
  • 5343 - Delete project error message does now display the teams blocking the deletion
  • 5346 - Automatic lifecycle promotion after automatic release creation works regardless of the permissions of the user that pushed the package, fixing an issue introduced in 2019.1.0
  • 5349 - Expose ephemeral storage requests and limits in K8S
  • 5351 - Using Tentacle Manager to configure a polling Tentacle does not authenticate with username/password has been fixed
  • 5352 - Fixed an issue where nodes with very long names would show StringTooLongException warnings in the log and were unable to elect a Leader node
  • 5354 - Improve user experience adding a worker when at license limit

Changes in Octopus 2019.2.2

  • 2852 - Added warning to Sensitive text fields regarding ##{ characters escaping
  • 4373 - The environments drop down now updates when selecting a different channel on the variable preview
  • 5340 - No longer logging warnings when private keys are not available when doing a Service Fabric deployment
  • 5344 - UI adding a confirmation to all "Upgrade Tentacle/Calamari" bulk actions
  • 5345 - Resolved issue with HCL templates failing validation in Apply Terraform step
  • 5358 - Fixed "Object reference not set to an instance of an object" when calling /api/projects/all
  • 5359 - Invalid certificates already present before 2018.2.0 release may cause /api/certificates/all request to fail
  • 5362 - Fixed a bug where upgrading from old versions of Octopus (pre 3.15.0) would fail

Changes in Octopus 2019.2.3

  • 4243 - Cloning a project now copies all project settings correctly
  • 4349 - Reduce confusion around the select and deselect options for steps excluded from a deployment
  • 4685 - Fixed issue where the "new server version" notification was not appearing
  • 5322 - Fixed issue where Check Tentacle Health summary was not showing details when all targets ended up as HasWarnings or Unhealthy
  • 5357 - Modified the tooltip text for Space and System team chips to make it easier to understand
  • 5363 - Re-indexing the in-built package repository can now run on any node in a multi-node cluster
  • 5364 - Fixed an issue where users without TeamView could not view the configuration for a Space
  • 5366 - Allow deployment of raw YAML to K8S Cluster
  • 5367 - Corrected an issue where the certificate archive would show incorrect results when loading the second and subsequent pages
  • 5368 - Updated the Space Switcher to highlight the active Space
  • 5369 - Added a link to the Space Switcher to allow easy space creation
  • 5371 - Fixed a bug where you could not fetch artifacts for releases with a large number of deployments
  • 5374 - Fixed an issue where the AWS Account variable selector wasn't being displayed
  • 5377 - Allow collapsing environment variables for project variable templates when browsing project variables on a tenant
  • 5378 - Task Queue startup code handles now exceptions correctly

Changes in Octopus 2019.2.4

  • 5208 - Fixed an issue where guided failure does not fail a deployment on the first attempt
  • 5356 - Re-wording message that shows up when a task is suspended because the space queue was stopped
  • 5373 - Added client side input validation for retry attempts in external feeds
  • 5375 - Filter in Teams page should only render after all teams have loaded
  • 5380 - UsernamePassword authentication now accepts email address
  • 5383 - Fixed feed refresh button crashes in several built-in steps
  • 5392 - Sorted the output of show-configuration and the root api responder to make it easier to find things
  • 5393 - fixes an exception during some upgrades due to incorrect assumptions in the UserRole data model
  • 5396 - Migrator.exe no longer fails when importing snapshot VariableSet referencing deleted certificate
  • 5397 - Migrator now remaps deployment action worker pool ID when importing

Changes in Octopus 2019.2.6

  • 5410 - Fixed crash on node --drain command
  • 5411 - Fixed issue with subscription webhooks using wrong http header type
  • 5414 - Fixed startup issue for a subset of customers by a data consistency script in 2019.2.5

Changes in 2019.2.5 (release was disabled/hidden due to a bug found)

  • 4821 - Fixed issue where expired cron expressions for scheduled deployments were throwing exceptions
  • 4916 - Renamed 'Run a Helm Update' step to 'Upgrade Helm Chart'
  • 5140 - Fixed issue where worker health checks run for deployment targets instead
  • 5370 - Cleaned up callouts in Space Edit screen to improve UX
  • 5379 - fixes scoping for projects when a different project group is scoped on the user role
  • 5381 - Environment section text only shows up if there are environments created on that Octopus instance
  • 5387 - fixes project scoping for user roles when scoped to the projects' group
  • 5391 - fixes dashboard bug when accessing projects in a group the user doesn't have access to
  • 5400 - Added target name to Calamari/Tentacle upgrade task name
  • 5401 - Fix for permission errors when trying to view another users permissions if you do not have access in another space
  • 5405 - Improved cross document links for ScopedUserRoles to Teams and UserRoles in Audit

Changes in Octopus 2019.2.7

  • 5285 - Added validation to ensure machine policy timeouts
  • 5407 - Added ability to supply additional arguments in Upgrade Helm Chart step
  • 5409 - Tags entered but not added are now auto-added when saving a tenant tag set
  • 5413 - Added the ability to filter by project and environment on the tenants overview
  • 5417 - Removed unnecessary Tenant Preview buton on Tenant Overview page
  • 5418 - Fix issue where side bar navigation was missing on the Create Subscription page
  • 5420 - Improved the processing speed of the auto-deploy triggers background process

Changes in Octopus 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

Changes in Octopus 2019.3.0

2019.3 LTS

Changes in Octopus 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 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 and VariableEditUnscoped permissions (CVE-2019-11632)

Changes in Octopus 2019.3.3

  • 5531 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined