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.

Highlights

These are the most important features you'll get by upgrading from 2019.4.1 to 2020.2.15

Octopus 2019.4

Highlights

  • Build information and work item tracking captures work items and build details and surfaces them with links to the appropriate sites.
  • Generate and share release notes automatically enables teams to view and share the work items associated with releases and deployments.
  • Octopus integration with Jira which provides two-way links between your Jira issues and your deployments.

Read our blog post to learn more.

Breaking Changes

There are some very slight changes to the format of the output returned by the Octopus.Server.exe show-configuration command. This is unlikely to affect you, but if you are using this to drive automation, please test the new release before upgrading.

Octopus 2019.5

Highlights

  • Updated build information and work item tracking to fix bugs and improve release note generation
  • Expanded script module support for C# (and F# and Bash and Python)

Read our blog post to learn more.

Breaking Changes

  • Remove the uniqueness restriction on user email addresses to support some customers who have Active Directory configurations where users share email addresses.

  • Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.

  • The OnlyConnectivity option that was configured on SSH health check policies is now a policy-wide setting. This setting is commonly used for raw scripting on SSH targets. If you are using this setting a new machine policy will be created during the Octopus Server upgrade. Please refer to this GitHub issue for details, you may need to take action.

  • Permissions are now more strictly enforced for creating and modifying teams and users, to avoid users being able to escalate their own permissions. Please see 5537 for more information.

Octopus 2019.6

Highlights

  • Build information and work item tracking captures metadata about work items and build details and surfaces them with links to the appropriate sites.
  • Release notes templates and automatic release notes generation makes it easy to generate and share the changes that are going into your releases.
  • Octopus integration with Jira which provides two-way links between your Jira issues and your deployments.
  • Expanded Script Module support for C#, F# and Bash and Python.
  • Linux Tentacle early access unlocks the ability to deploy to Linux servers in highly secure environments where inbound ports cannot be opened on production servers.

Read our [Octopus 2019.6 blog post to learn more.

Breaking changes

This release includes the following breaking changes:

  • There are some very slight changes to the format of the output returned by the Octopus.Server.exe show-configuration command. This functionality is unlikely to affect you, but if you are using this to drive automation, please test the new release before upgrading.
  • To support some customers who have Active Directory configurations where users share email addresses, we have had to remove the uniqueness restriction on user email.
  • Health check properties of machine policies have changed to accommodate Linux Tentacle. TentacleEndpointHealthCheckPolicy has been renamed to PowerShellHealthCheckPolicy and SshEndpointHealthCheckPolicy has been renamed to BashHealthCheckPolicy. Any custom tools that create machine policies should use the new property names.
  • The SSH health check policy OnlyConnectivity configuration option is now a policy-wide setting. Raw scripting on SSH targets commonly uses this setting. If you are using this setting, Octopus will create a new machine policy during the upgrade. Please refer to this GitHub issue for details if this is relevant to you.

Octopus 2019.7

Highlights

Octopus 2019.7 is a significant release even though it doesn't include any user-facing features. It includes technical changes to retarget Octopus Deploy to .NET Framework 4.7.2 and .NET Core 2.2 so Octopus can run natively on Linux and in Linux containers. This change is initially for Octopus Cloud and it will be extended to Octopus self-hosted in the future.

Watch our blog for some great technical blog posts on what this involved and our lessons learned.

Breaking changes

Most customers can upgrade directly to Octopus Server 2019.7, except those hosting Octopus Server on Windows Server 2008 SP2. This blog post has more details about who will be affected, and what you can do to upgrade.

Don't worry, the Octopus Server installer will prevent you from accidentally upgrading if your host operating system will not be supported.

Octopus 2019.8

Highlights

2019.8 includes:

  • Improved deployment process editor: Quickly jump between steps when editing the deployment process
  • Cloning Tenants
  • More health check scheduling options: Health checks can be configured to run on a cron expression, or to never run
  • Allow overriding namespace in Kubernetes steps
  • New Variable Filter expressions: Trim, Substring, Truncate, UriEscape, UriDataEscape
  • Copy and paste to add certificates: Certificates can now be pasted as text directly into the portal

See our blog post for the full details.

Breaking changes

No breaking changes in this release.

Octopus 2019.9

Highlights

  • Streamlined deployment process editor with better visibility of your entire deployment process and fewer clicks to navigate between steps.
  • Added support for Tentacle for Linux to improve the flexibility of Linux deployments including support to deploy to highly secure environments where it’s not possible to open port 22.
  • Tenant cloning for faster configuration of new Tenants.
  • Added health check scheduling options so they can be configured to run on a cron expression, or to never run.
    • Added support to override namespace in Kubernetes steps.
    • New Variable Filter expressions including Trim, Substring, Truncate, UriEscape and UriDataEscape.
    • Added support to paste to certificates as text to add certificates directly in the portal.

Read our blog post to learn more.

Breaking changes

This release includes a single breaking change as Octopus Server no longer supports for Windows Server 2008 SP2.

Octopus 2019.10

Highlights

Flexible Linux deployments, PowerShell Core support, Operations RunBooks EAP

  • Tentacle for Linux enables deployments to highly secured servers without opening port 22 in production environments
  • Built-in PowerShell Core support for both Windows and Linux platforms
  • Improved build information and work item tracking
    • Package metadata has been renamed to Build Information and promoted to a top level section in the Octopus Library.
    • Added support for deployment change templates so you can customize the structure of your deployment changes.
  • Simpler package-based step templates whereby we show our package selector when a package-based step template is added to a project
  • Early access to Runbooks for Operations teams enabling teams to run emergency or routine operations tasks in a first-class way

Read our blog post to learn more.

Breaking changes

PowerShell Core

PowerShell Core support has introduced a change where running PowerShell scripts against non-Windows targets no longer silently ignores .ps1 files. Octopus will now attempt to execute .ps1 files on deployment targets. If PowerShell Core is installed on those targets, this may change the behaviour of your deployments. If PowerShell Core is not installed on those targets, the deployment will fail.

Build Information

Our build information change involved renaming resources from the API through to the database. This is generally backwards compatible, however anyone using our GitHub issue tracker will need to ensure they upgrade their Octopus Server if they upgrade their Azure DevOps extension, TeamCity plugin, or Bamboo plugin.

Octopus 2019.11

Highlights

Official Jenkins Plugin and Operations Runbooks

  • Official Octopus Deploy Jenkins plugin enables teams to integrate their Jenkins builds with Octopus deployments.
  • Operations Runbook platform helps teams automate routine maintenance and emergency operations tasks like infrastructure provisioning, database management, and website failover and restoration.
    • Familiar configuration process for anyone who has configured a deployment process.
    • The ability to execute runbooks directly against infrastructure on-demand or on a schedule (nightly, weekdays, once a month, etc.) as per your team’s needs.
    • Runbooks can be parameterized with prompted variables.
    • You can make changes to your runbooks with confidence, and only publish them after they have been safely tested.
    • Runbooks are managed and executed by Octopus, so this means there’s a complete audit trail that can be reviewed at a later date, making it easy to see what happened, when and why, and if anything needs to be changed.
    • You can give your entire team permission to execute your runbooks, without assigning everybody on the team permissions for the infrastructure the runbooks will execute against.

Breaking changes

Octopus API and Octopus.Client

The Octopus API has changed as a part of this release, versions of Octopus.Client before 8.0.0 can not create scheduled triggers on an Octopus Server where the version is older than 2019.11.0.

Octopus 2019.12

Highlights

Operations Runbooks, Jenkins plugin, PowerShell Core support, improved build server integration and more!

  • Operations Runbook platform for automating routine maintenance and emergency operations tasks. Runbook examples include infrastructure provisioning, database management, and website failover and restoration.
  • Official Octopus Deploy Jenkins plugin enabling teams to integrate their Jenkins builds with Octopus Deployments
  • Built-in PowerShell Core support for both Windows and Linux platforms
  • Improved build information and work item tracking
    • Package metadata has been renamed to Build Information and promoted to a top level section in the Octopus Library.
    • Added support for deployment change templates so you can customize the structure of your deployment changes.

Read our blog post to learn more.

Breaking changes

This release includes the following breaking changes.

Octopus API and Octopus.Client

The Octopus API has changed as a part of this release, versions of Octopus.Client before 8.0.0 can not create scheduled triggers on an Octopus Server where the version is older than 2019.11.0.

PowerShell Core

PowerShell Core support has introduced a change where running PowerShell scripts against non-Windows targets no longer silently ignores .ps1 files. Octopus will now attempt to execute .ps1 files on deployment targets. If PowerShell Core is installed on those targets, this may change the behaviour of your deployments. If PowerShell Core is not installed on those targets, the deployment will fail.

Build Information

Our build information change involved renaming resources from the API through to the database. This is generally backwards compatible, however anyone using our GitHub issue tracker will need to ensure they upgrade their Octopus Server if they upgrade their Azure DevOps extension, TeamCity plugin, or Bamboo plugin.

Octopus 2019.13

Octopus 2019.13.0 is an incremental release after we shipped Octopus 2019.12.0 with long term support (LTS). It contains small updates and bug fixes as per the release notes. The next minor release will be 2020.1.0 and it will include features on our public roadmap.

Octopus 2020.1

Highlights

DarkMode, Improved Octopus CLI support on macOS and Linux, and environment specific Worker Pools.

Read our blog post to learn more.

Breaking changes

This release includes the following breaking changes.

  1. Octopus Server minimum requirements - Octopus 2020.1 raises the minimum requirements for running Octopus Server to Windows Server 2012 R2 and SQL Server 2017.
  2. Library variable set permission changes - You can now scope variables stored inside library variable sets to environments and tenants, giving you fine-grain permissions and more consistent access control.

NOTE: Octopus Server has been ported to .NET Core 3.1 and so it no longer requires the .NET Framework to be installed.

Octopus 2020.2

Highlights

Execution containers for workers (EAP), Jira Service Desk change requests, better run conditions and fast variable lookups with our improved code editor.

  • Execution containers for workers let you execute deployment work in isolation without the need to manage dependencies and containers.
  • Integrated change management with Jira Service lets teams create change requests during their deployment automatically.
  • Better run conditions adds deployment process improvements, including rolling deployment and machine level variable conditions.
  • Fast variable lookups with our improved code unlocks the ability to quickly add Octopus variables into your custom scripts without touching the mouse.

Read our blog post to learn more.

Breaking changes

Octopus 2020.1 introduced updated minimum requirements for running Octopus Server to Windows Server 2012 R2 and SQL Server 2017. This release is now enforcing the SQL Server minimum requirements.

This version also introduced a breaking change for users of Active Directory authentication using Kerberos, there is now a requirement to use host machine SPNs rather than user SPNs. This requirement means that High Availability features can only be used with NTLM based authentication when using Active Directory integration with H/A/

Details

Changes in Octopus 2019.4.1

  • 4236 - Auto Release Creation and Scheduled Triggers now evaluate variables in package names
  • 5412 - Auto Release Creation and Scheduled Triggers can now create releases for projects using Step Templates that reference packages other than the one uploaded
  • 5421 - Improved the speed of the Machine status triggered AutoDeploy
  • 5424 - UI trimming roles on data-entry to avoid white-space issues during machine scoping
  • 5445 - Package push with overwrite now updates metadata
  • 5447 - Swagger file should use string for enums
  • 5449 - Integrate Octopus with Jira to get deployment feedback on your Jira work items
  • 5450 - Projects can now specify a release notes template, complete with variable binding, that gets applied during release creation
  • 5465 - Fixed bug in release creation when steps are scoped to channels

Changes in Octopus 2019.4.2

  • 5159 - Add Octo.exe argument --noDeployAfter to set QueueTimeExpiry
  • 5419 - An event is now logged to the audit log when a task is cancelled due to the server shutting down unexpectedly
  • 5426 - Certificate with private-key being displayed as not having private-key
  • 5427 - UI adding default role chips to the variable editor when no target roles exist yet
  • 5429 - Adding project group filtering for events/subscriptions
  • 5430 - Fixed an issue where an excessive amount of requests were being made for tenant tag sets when on the deployment target settings page
  • 5435 - UI show the step type while editing a step
  • 5436 - Tenant tag selection now shows an appropriate message when all tag sets are empty
  • 5440 - Prevented duplicate validation messages
  • 5452 - Improve Performance of Dashboard by indexing temp table
  • 5455 - Improved the performance the Projects API when many projects use features that are based on step names
  • 5461 - UI adding form expander animations

Changes in Octopus 2019.4.3

  • 5223 - Fixed an issue where redeploying a SF application of the same app/type/version would fail regardless of override behavior
  • 5386 - UI adding categories to make step template selection more intuitive
  • 5402 - Related to 5468, Azure Resource Group template parser updated to handle non-string types
  • 5415 - Added warning when user is creating/editing an Email Step or a Subscription and SMTP hasn't been configured yet
  • 5431 - Prevented disabled steps from being used for release versioning and automatic release creation
  • 5437 - Updated health check messages to better reflect plural and singular
  • 5444 - Octopus Server can no longer be started against a database with a newer schema
  • 5468 - Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
  • 5472 - Corrected read-only summary label for container volume mount in k8s deploy containers step
  • 5473 - Ensure only distinct package versions are included when running package metadata retention
  • 5475 - Button styling has been updated to improve accessibility
  • 5478 - Resolved spurious validation failure related to secret volume on deploy k8s containers step
  • 5480 - Add certificate variable validation for HTTPS binding on the Deploy to IIS step
  • 5481 - Bug: Unable to pull docker image on some ssh targets
  • 5485 - Kubernetes step resource validation is over-eager and not allowing variables

Changes in Octopus 2019.4.4

  • 5483 - Changed all popover components to use the new MUI component which is reported to fix the positioning delay
  • 5487 - Return a more helpful error message on the release page if a package / version combination cannot be found in the built-in repository
  • 5490 - Make package published date format in UI consistent and include tooltip with timezone info
  • 5491 - Fixed exception on Project settings page if auto release creation is enabled and a package step is configured to use a versioning template instead of package step
  • 5493 - BugFix: DockerHub feeds fail to authenticate during acquisition

Changes in Octopus 2019.4.5

  • 4567 - Automatic Release Creation now creates releases after a step rename
  • 5394 - K8S deploy step supports external secrets to be used for ingress TLS
  • 5458 - Improved the speed of the automatic release creation after a package upload
  • 5488 - Release note accumulation honors the Discrete Channel release setting on the project
  • 5494 - Raw commit details as an Octopus variable for release notes
  • 5495 - Work item release notes from GitHub / Jira
  • 5498 - Improved error message when attempting to acquire helm charts but helm is missing
  • 5501 - Fixed an issue preventing the cloning of a step into the current project
  • 5506 - Fixed issue with creating releases when multiple packages exist on the versioning step

Changes in Octopus 2019.4.7

  • 5482 - Fixed a bug preventing deployment target triggers from working when any project has more than one deployment target trigger defined
  • 5511 - Releases and deployments now have access to a distinct list of work items, as well as the original hierarchical data structures
  • 5515 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
  • 5518 - Added support for Azure accounts in Terraform steps
  • 5521 - Work items with an alphanumeric project identifier in issue ID can now be parsed
  • 5528 - Fixed an access control bug where project scoping was not being applied for VariableViewUnscoped and VariableEditUnscoped permissions (CVE-2019-11632)
  • 5532 - Fixed single quotes arguments passed to Terraform

Changes in Octopus 2019.5.0

  • 3590 - Choosing a certificate no longer shows the binding expression toggle in the UI
  • 5462 - Added variables for trigger which caused a deployment
  • 5486 - UI improving delta highlighting on the audit screen
  • 5499 - Script modules are now supported for Bash, C#, F# and Python
  • 5502 - Fixed an issue where the file picker window would not trigger from the replace certificate dialog
  • 5507 - UI improving onboarding for new users and team membership and including a list of teams on the users page
  • 5508 - Can now step into script modules while debugging PowerShell script steps
  • 5520 - UI Dashboard screen search bar will no longer render if there are no Environments in the instance
  • 5522 - Release notes evaluation now also happens for automatic release creation and scheduled release triggers
  • 5523 - Fixed an issue where Deploy CloudFormation template step would fail when using the change sets feature and no changes need to be applied
  • 5524 - Fixed bug where retrieving release notes from GitHub would throw an exception if the VcsRoot ended with .git
  • 5526 - Improved how the Portal retries connecting when the Octopus Server is not contactable
  • 5533 - Health check may fail on windows machines with failure to load TimeZoneInfo type
  • 5534 - The Test button on the Create Feed screen no longer crashes when invalid data entered
  • 5536 - Fixed error when attempting to delete an Octopus Server node
  • 5537 - Modifying teams and roles enforces all permissions and scoping in elevation checks
  • 5540 - Added confirmation dialog before deleting an API Key
  • 5542 - Fixed an issue preventing the selection of the Specific Version radio button when using variables for the package feed
  • 5544 - Breaking change Some machine policy properties have been renamed to better accommodate Linux Tentacle
  • 5546 - Fixed TypeError on Kubernetes step when adding a volume
  • 5549 - Octopus no longer enforces email uniqueness across users, in order to support Active Directory scenarios where users can share an email address

Changes in Octopus 2019.5.1

  • 5550 - Fixed an issue where multi-select and auto completion fields would render popovers partially offscreen when close to the edge
  • 5551 - Deployment retention no longer requires exclusive access to the tentacle (this bug was introduced in 2019.4.5)
  • 5555 - Fixed "Sequence contains no elements" error when viewing releases that don't match the current project release versioning settings
  • 5556 - Fix terraform steps unable to asume AWS service roles
  • 5557 - Only load script module usage on demand
  • 5559 - Include monthly active user count in usage statistics

Changes in Octopus 2019.5.2

  • 5539 - Fixed missing navigation menus when creating a new Deployment Target or Worker

Changes in Octopus 2019.5.3

  • 5567 - Rolled back the logging changes in 2019.4.3 that are likely causing deployments, tasks and server shutdown to hang

Changes in Octopus 2019.5.4

  • 5476 - Fixed high CPU usage on deployment task page
  • 5512 - Prompted variables without a label can now only be scoped to environments
  • 5513 - Fix an issue where multiple error panels will be displayed when server is unreachable
  • 5538 - Updates and usage telemetry settings were moved from the setup wizard to the Portal
  • 5545 - Fixed an issue where the Tentacle poll-server command was unable to successfully configure polling on second and subsequent HA nodes
  • 5547 - ARM template parsing handles parameter types in a case insensitive manner
  • 5560 - Fix terraform commands not generating any output during deployments
  • 5562 - Update CloudFormation change set fields to be bindable
  • 5564 - Automatic release creation can no longer be configured to use a package sourced from an external feed
  • 5569 - Adds a summary view of variable set usage in projects and releases
  • 5570 - UI adding a typed confirmation to the delete project action for additional safety
  • 5573 - Added ability to turn off variable substitution for Terraform default files in package

Changes in Octopus 2019.5.6

  • 3859 - IIS bindings with upper case protocols are now show correctly in the IIS Manager
  • 3903 - The IIS binding list on the step edit now shows the value of the enabled flag
  • 4735 - Provide warning if email body fails to evaluate variables
  • 4779 - API keys are now immediately removed from the server cache when a user is disabled or deleted
  • 5228 - Offline drops now escape Windows and Linux special characters on all platforms
  • 5264 - UI fix for dialog overflow and scrolling issues
  • 5342 - Support escaped quotes in octostache variable filter parameters
  • 5558 - Now when a Tentacle is deleted from Octopus all connections to that machine will be closed
  • 5568 - Fix for the migration API pushing packages to a destination server
  • 5572 - Fixed bug that caused automatic release creation failures to return 400 and 500 on package push
  • 5579 - Fix for API key not being copied to the clipboard in the generate new API key dialog
  • 5581 - Fix an issue where autocomplete popover does not close after selecting an item
  • 5582 - Fix an issue where autocomplete and multi selects would not select an item when pressing enter after focusing an item in the list
  • 5584 - Fixed bug where emails fail due to certificate error when SSL/TLS is disabled in SMTP configuration
  • 5586 - Guest authentication provider now supports automatic logins
  • 5588 - Allow all feed types to select non acquisition option during script steps
  • 5464 - Cleanup tasks are no longer scheduled when the task queue for a space is stopped
  • 5583 - Package build metadata, e.g. VcsCommitNumber, is now included in deployment variables
  • 5587 - Label validation in K8S steps does not allow for prefixes
  • 5591 - Editing a space is now validated and space name length validation messages improved

Changes in Octopus 2019.5.7

  • 5592 - Labels in custom resources now take precedence over the global labels defined in the container deployment step
  • 5596 - Projects with no alpha-numeric characters will now generate a non-blank slug
  • 5598 - Fixes a bug introduced in 2019.5.4 that prevented most API requests from being handled in parallel, causing slow downs of the API and UI

Changes in Octopus 2019.5.8

  • 4564 - Deployments awaiting manual intervention block other deployments to the same environment
  • 4619 - Update Calamari to .Net Core 2.2
  • 4781 - When deleting or purging a directory, once the retry limit has been exceeded once, subsequent deletes will only be tried once
  • 5197 - The CertificateReplace, TaskState, and VersionRuleTest endpoints no longer treat the requests JSON properties as case sensitive
  • 5566 - Fixed order of tenant tagset tags on Infrastructure dashboard
  • 5578 - Server configuration files can now be referenced using a UNC path
  • 5599 - Expanded the input fields for command parameters
  • 5603 - Fix an issue where tabs pushed onto the browser history a number of times causing issues when navigating back

Changes in Octopus 2019.5.9

  • 4209 - Show "Update variables" button on a release even if it doesn't have existing variables
  • 4836 - Fix error on Scheduled Triggers if user doesn't have access to all environments for project
  • 5372 - Fix for auto-deploy machines becoming available during a deployment
  • 5484 - Add support for dynamic project IDs in Deploy Release steps when working with package metadata in releases
  • 5577 - Add support for dynamic package IDs when working with package metadata in releases
  • 5584 - If SMTP is configured to use SSL/TLS and initial connection using SSL fails, we try to connect using TLS instead. If SMTP is not configured to use SSL/TLS we intially try to connect using TLS but if that fails we connect using an insecure connection
  • 5600 - Display escape characters in log if an Azure account can't be found by ID
  • 5609 - Fix for Object reference not set to an instance of an object. when saving ARC, project settings, Life Cycles, Library Variable Sets when ARC is configured with a step that doesn't have a primary package
  • 5611 - Incorrect permission elevation error when saving a team
  • 5612 - UI introducing a help sidebar to provide more context
  • 5613 - Improved handling of login identity checks when using Directory Services, to accommodate cases where users have ended up with multiple attached identities
  • 5614 - Redeployments now include package metadata for the releases used the first time the deployment's release was deployed to the given environment/tenant
  • 5616 - Use native kubectl config masking for verbose logs
  • 5618 - Active directory group search now works on the group name containing the entered value, rather than only starting with the entered value

Changes in Octopus 2019.5.10

  • 4227 - Fixed a memory leak that occurs when WebSocket polling tentacles do not trust the server's certificate
  • 4822 - Allow updating worker pool on child steps
  • 5619 - Scheduled, Triggered and Auto-Promoted deployments now always respect the guided failure setting on the project and environment

Changes in Octopus 2019.5.12

  • 4964 - Added special variable OctopusUseBundledAwsCLI to allow opting out of using the bundled AWS CLI
  • 5360 - Added special variable OctopusUseBundledAwsPowerShellModules to allow opting out of using the bundled AWS PowerShell modules
  • 5395 - Update bundled AWS CLI to 1.16.178
  • 5466 - Variable selector on tenant variables now includes variables from the selected project
  • 5467 - Variables supplied from parent to child projects with Deploy Release steps will correctly have a higher specificity score now allowing them to always overwrite child variables
  • 5474 - Added an option to merge instead of replace IIS bindings
  • 5575 - Fix for TypeError on certificate search, when certificate data was in an unexpected state
  • 5584 - If SMTP is configured to use SSL/TLS and initial connection using SSL fails, we try to connect using TLS instead. If SMTP is not configured to use SSL/TLS we intially try to connect using TLS but if that fails we connect using an insecure connection
  • 5589 - Fix for audit entries on variables where no changes were made
  • 5608 - Fixed bug that was preventing Automatic Release Creation from running when an unrelated package was of a higher version than the package specified for ARC
  • 5621 - Fix issue where filter in dropdown can’t be focused
  • 5624 - Bugfix paging through docker registry results
  • 5626 - Tentacle has wriggled into the Linux category for deployment targets and workers
  • 5630 - Fixed issue where usage of Token account variables was not shown correctly in the UI
  • 5631 - Updated bundled Tentacle which has improved connection retry logic and certificate import improvements
  • 5632 - Fixed an issue with boolean handling in the Azure Resource Group template step's code editor
  • 5637 - Service Fabric profile flag to disable upgrades is now honoured
  • 5638 - Added report about executing threads stacks as part of Diagnostics zip
  • 5641 - Fixed a bug where Octopus can take a long time to connect to deployment targets

Changes in Octopus 2019.6.0

  • 5651 - Added validation to the IIS configuration to ensure a hostname is entered when SNI is enabled
  • 5650 - Show error message when kubectl returns error message

Changes in Octopus 2019.6.1

  • 5663 - Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available

Changes in Octopus 2019.6.2

  • 5665 - Fix an issue where it was not possible to select a certificate or account when using tenant variables

Changes in Octopus 2019.6.3

  • 5671 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
  • 5673 - Fixed an issue where the UI would prevent you from selecting an environment to deploy to if your DeploymentCreate permissions were scoped to tenants
  • 5675 - Deployments awaiting manual intervention will no longer block other deployments to the environment by default. This behavior can now be controlled by a switch on the manual intervention step

Changes in Octopus 2019.6.4

  • 5682 - Fixed an issue where server would fail to start due to incompatibility checks after upgrading from older versions
  • 5697 - Wildfly deployments working again

Changes in Octopus 2019.6.5

  • 5703 - Fix for Project Deploy Release page appears to hang with a large number of tenants
  • 5705 - Fix for incorrectly migrated user roles that could not be saved due to validation error
  • 5708 - Create correct commit links in Octopus when using git@<host>: URLs in the VCS root in package metadata
  • 5715 - Fix for project and project-group scoped permission UI issues
  • 5717 - Fix for Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
  • 5719 - Fix for Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables
  • 5738 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log - CVE: CVE-2019-14268

Changes in Octopus 2019.6.6

  • 5724 - Improved parsing of Jira issue references, and only display Jira issues that exist in the configured Jira instance (requires a username and password to be configured on the Jira issue tracker settings page)
  • 5753 - Fixed some sensitive value handling in the server config API/portal UI - CVE: CVE-2019-14525

Changes in Octopus 2019.6.7

  • 5749 - Tentacle TentacleProxyPassword logged in clear text when OctopusPrintVariables is set
  • 5760 - TentacleProxyPassword logged in clear text if $env:HTTP_PROXY is printed and password contains special characters

Changes in Octopus 2019.6.8

  • 5765 - Resolved issue where extracting template from deployment step could result in 'Given key not present in dictionary' error
  • 5786 - Fixed a bug that prevent upgrades when malformed artifact documents exist
  • 5809 - Fixed a null reference exception that occurred on login in some AD configurations after upgrade beyond 2019.5.0

Changes in Octopus 2019.6.9

  • 5850 - Handle bad Auto Release Creation configuration better and allow users to resolve it
  • 5856 - Resolved issue saving deploy kubernetes containers step when memory requirements set but not cpu

Changes in Octopus 2019.6.10

  • 5932 - Fixes rare crash in editing a package deployment step if a large amount of feeds are present

Changes in Octopus 2019.6.11

  • 5956 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages - CVE: CVE-2019-19084
  • 5959 - Fixed a stored cross-site-scripting (XSS) vulnerability - CVE: CVE-2019-19085

Changes in Octopus 2019.6.12

  • 5962 - Upgraded Let's Encrypt support to ACME v2

Changes in Octopus 2019.6.13

  • 5982 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages on Octopus Cloud - CVE: CVE-2019-19084

Changes in Octopus 2019.6.14

  • 5996 - CSRF cookie sometimes missing secure attribute - CVE: CVE-2019-19375
  • 6000 - Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
  • 6003 - Invalid request submitted to Team API can cause denial of service - CVE: CVE-2019-19376

Changes in Octopus 2019.6.15

  • 6077 - Backport Fix - The WebUI HTTP listener now retries if there is a network error that causes it to terminate

Changes in Octopus 2019.7.0

  • 4802 - Added validation to the IIS configuration to ensure a hostname is entered when SNI is enabled
  • 5503 - Show error message when kubectl returns error message
  • 5504 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
  • 5602 - Fixed paging on the user activity feed
  • 5642 - Clarified error message shown when a recursive variable definition is detected
  • 5645 - Fix for team deletion issue with email steps
  • 5646 - Removed ProjectGroupId from Deployment as this was not being kept in sync during Project moves (to other project groups), and causing octo.exe to fail to import
  • 5653 - Accounts referenced by targets used in a deployment manifest are now shown in account usage
  • 5654 - Made displaying usage more consistent and performant
  • 5656 - Fixed dirty state checking on Deploy an ARM Template step
  • 5657 - Fixed the logic in Azure Service Fabric deployments to determine if upgrades are available
  • 5658 - Account usage for Token, Username/Password and SSH Key Pair account types now show all available usage types, not just usage in targets
  • 5659 - Consolidated release usages and release snapshot usages for account types for clarity
  • 5660 - Added the ability to delete a specific deployment
  • 5664 - Fix an issue where it was not possible to select a certificate or account when using tenant variables
  • 5666 - Deployments awaiting manual intervention will no longer block other deployments to the environment by default. This behavior can now be controlled by a switch on the manual intervention step
  • 5669 - Fixed an issue where the UI would prevent you from selecting an environment to deploy to if your DeploymentCreate permissions were scoped to tenants

Changes in Octopus 2019.7.1

  • 5509 - Adding friendly landing page for users with no permissions to see Environments
  • 5667 - UI adding configuration to control features of the help sidebar
  • 5678 - Hidden folders are now ignored when migrating to Spaces new packages folder structure
  • 5679 - Fixed an issue where server would fail to start due to incompatibility checks after upgrading from older versions
  • 5684 - Update msi installer to check for .NET 4.7.2
  • 5685 - UI adding actions to add another target/worker for easier data entry

Changes in Octopus 2019.7.2

  • 5617 - Increased timeout for downloading external NuGet feeds from 60s to 1hr
  • 5668 - Prompted variables are now ordered alphabetically when creating a deployment
  • 5681 - Allow library step templates to be deleted when referenced in releases
  • 5686 - In some cases the task progress percentage was not reported in the log
  • 5689 - Resolved issue where extracting template from deployment step could result in ‘Given key not present in dictionary’ error
  • 5692 - Fix issue where changing tabs in a library step template based on a script step would error when choosing to to use a script in a package
  • 5696 - Added helper functions to write progress bar messages to the deployment log
  • 5698 - Update UI and calculation of matched records on dashboard
  • 5699 - Sensitive variables in step properties are no longer cleared when a step is enabled
  • 5701 - Fix for incorrectly migrated user roles that could not be saved due to validation error
  • 5716 - Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
  • 5718 - Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables

Changes in Octopus 2019.7.3

  • 4394 - Improved the variable preview screen to make it clearer how it works and ensured all variable types were displayed correctly
  • 5634 - Fixed disposing of leases for external workers with packages
  • 5652 - Added default roles for build servers
  • 5704 - Fixed license check code to deduplicate tentacles and ssh endpoints
  • 5707 - Create correct commit links in Octopus when using git@<host>: URLs in the VCS root in package metadata
  • 5710 - Fix for project and project-group scoped permission UI issues
  • 5714 - Fix for DeploymentQueued event not being created with ARC
  • 5720 - Fix for Project Deploy Release page appears to hang with a large number of tenants
  • 5739 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log - CVE: CVE-2019-14268

Changes in Octopus 2019.7.5

  • 5709 - S3 Special Header Content-Type not being set properly
  • 5723 - Improved parsing of Jira issue references, and only display Jira issues that exist in the configured Jira instance
  • 5725 - Updates to Audit Filtering
  • 5744 - Fixed an issue where UI feature toggles were misbehaving
  • The following issues were rolled forward from 2019.7.4 release (that was pulled due to a feature toggle issue):
  • 5406 - Migrator import command won't load variable sets associated with deployments
  • 5732 - Update Dashboard to fix bug in configuring limited rows
  • 5734 - Library Variables Sets are now displayed again
  • 5735 - Fix an issue where multiple overflow menus can be open at the same time
  • 5740 - Fixed a bug where you could not search for Docker images using DockerHub external feeds

Changes in Octopus 2019.7.6

  • 4418 - Deploy a Release steps can now be used in rolling deployments
  • 5620 - UI fixing anchor-links in the task summary list
  • 5713 - Automatic health checks can now be disabled or scheduled using a cron expression
  • 5729 - Fix issue with "all nodes offline" when a new instance is setup against an existing database
  • 5754 - Fixed some sensitive value handling in the server config API/portal UI - CVE: CVE-2019-14525

Changes in Octopus 2019.7.7

  • 5590 - Allow overriding namespace in Kubernetes steps
  • 5607 - Internal mapping improvements to increase tenant variable set endpoint
  • 5750 - Tentacle TentacleProxyPassword logged in clear text when OctopusPrintVariables is set
  • 5751 - Fix for partialName parameter searching on the artifacts API endpoint
  • 5761 - TentacleProxyPassword logged in clear text if $env:HTTP_PROXY is printed and password contains special characters
  • 5764 - Support providing certificates via porta by directly pasting as text

Changes in Octopus 2019.7.8

  • 5722 - Fix for slow performing release and deployment queries
  • 5762 - Added more information about target's status in the deployment preview screen
  • 5763 - Fixed issue where Tentacle Upgrades fail on servers that do not have .Net Framework 4.7.2
  • 5766 - Reduce the set of users editable with the UserEdit permission, such that this responsibility can be delegated to less privileged users
  • 5767 - Prevents multiple spaces being flagged as the default space via the API
  • 5768 - fix search boxes on Safari

Changes in Octopus 2019.7.9

  • 5772 - Metadata button only expands/collapses its own section
  • 5773 - Expose Docker Image labels as Project Variables
  • 5774 - Adds additional validation to the deployment process API to guard against PackageReference.Properties from accepting null values
  • 5777 - Fixed a memory leak with listening Tentacles
  • 5779 - Creating a space no longer requires AdministerSystem. SpaceCreate should be sufficient

Changes in Octopus 2019.7.10

  • 5674 - Fixed error creating release when using a Step Template that uses an Azure account parameter
  • 4232 - Fixed an issue where, in certain circumstances, sensitive variables could be exposed in the variable preview - CVE: CVE-2019-15698

Changes in Octopus 2019.7.11

  • 5776 - Fix flakey DateTime issue in Scheduling a Release - Now or Later
  • 5783 - Fixed warnings displayed when Wildfly apps are deployed with Java 9+
  • 5785 - Fixed an issue deploying a docker image that does not have labels

Changes in Octopus 2019.7.12

  • 5789 - Resolved an issue that prevented deployments to Cloud Regions

Changes in Octopus 2019.7.13

  • 5497 - Fixed a bug that prevent upgrades when malformed artifact documents exist
  • 5500 - Fix for scheduled release creation for variable package feeds
  • 5771 - Add connectivity verification buttons for Jira issue tracker settings
  • 5788 - Consecutive spaces in Projects and Spaces are now ignored during the "type the name to confirm" delete validation
  • 5792 - Force Upgrade option will create a new Service Fabric deployment if none exists
  • 5795 - The WebUI HTTP listener now retries if there is a network error that causes it to terminate
  • 5796 - Fix linking of Projects to Channels in Audit Log
  • 5800 - Module imports are now timed and printed as verbose log messages
  • 5804 - UI adding a side-by-side step-editing experience and filters

Changes in Octopus 2019.8.0

  • 5213 - Fix issue where Calamari doesn't respect the setting to bypass the default proxy in windows
  • 5726 - System.IO.IOException: The process cannot access the file 'xxx' because it is being used by another process during Calamari package extraction
  • 5727 - Add the ability to clone a Tenant
  • 5784 - Demote logging level for "Setting Proxy Environment Variables" to VERBOSE
  • 5793 - Moved --ServerNodeName from the configure command to the create-instance command
  • 5798 - Fixed a bug in ProjectSwitcher that was redirecting to the wrong projects after filtering results
  • 5805 - Fixed a null reference exception that occurred on login in some AD configurations after upgrade beyond 2019.5.0
  • 5806 - Allow configuration of a specific domain for cookies issued by server, to allow custom web UIs to call the API
  • 5811 - Add a description field to each Tenant
  • 5812 - Add UriEscape, UriDataEscape, Substring, Trim and Truncate filters for variable substitutions

Changes in Octopus 2019.8.1

  • 5813 - Jira comment parser RegEx updated to simplify and also remove some false positive cases
  • 5814 - Machine policy health check no longer runs at startup when health check policy is set to Never
  • 5815 - Fixed a performance problem where looking at a deployment paused by manual intervention would cause high CPU usage on the Octopus Server, but only if the manual intervention was not restricted to specific teams and you have a LOT of teams
  • 5816 - UI fix for accessing Project Templates menu for multi-tenancy
  • 5817 - UI fix for cloning steps across different projects
  • 5818 - Fixed a bug preventing new variable values from being added to a project or library variable set where there is already another variable value with the same name
  • 5819 - Made CTRL+Click work in the project switch again, so it opens the selected project in a new browser tab just like it did before 2019.7.13

Changes in Octopus 2019.8.2

  • 5647 - Package acquisition now runs after manual intervention for steps with additional packages
  • 5803 - Automatic redirect to secure WebUI binding now works for localhost binding
  • 5820 - Fix misaligned deployment process chips
  • 5825 - Certificates without a private key can now be installed into another user's key store on windows
  • 5826 - Fixed the User edit page so the Reset Password button is only enabled based on the same permissions checks logic the API is using
  • 5830 - Updated bundle Tentacle to 5.0.3 to fix crash when launching Tentacle Manager
  • 5834 - Includes bundled Tentacle 5.0.3 with fix for memory leak with Listening Tentacles

Changes in Octopus 2019.8.3

  • 5832 - Improved startup performance when many files exist in the Octopus Server directory
  • 5836 - Empty annotation, label, secret and configmap values are now passed through to K8S
  • 5839 - Includes bundled Tentacle 5.0.4 which includes the new Linux Tentacle

Changes in Octopus 2019.8.4

  • 5837 - Fixed issue where step delete silently fails when step is used in the versioning strategy
  • 5838 - Fixed replace option for Upload Package dialog and client backwards compatibility
  • 5841 - Fixed issue with tenant variable editing, which occurred if a team the user was in had a role scoped to an environment
  • 5844 - Fixed Octopus ID authentication provider's default configuration to stop warnings appearing in the server logs unnecessarily
  • 5847 - fix for NullReferenceException in CheckForOctopusUpgrade reported in server dignostic errors
  • 5833 - Added retry logic and configurable timeout to initial connection to SMTP host

Changes in Octopus 2019.8.5

  • 5846 - Show a nicer error instead of crashing when a bad value is passed to the command line for the --dependOn argument on the service command
  • 5849 - Handle bad Auto Release Creation configuration better and allow users to resolve it
  • 5852 - New installations of Octopus Server will have the built-in package repository re-index feature disabled by default
  • 5853 - Fix for incorrect Isolation Mutex causing deployments to block/hang
  • 5855 - Resolved issue saving deploy kubernetes containers step when memory requirements set but not cpu
  • 5857 - Made a data migration script more robust when faced with Auto Release Creation referencing a channel that has been deleted
  • 5858 - Description support on teams
  • 5859 - Fix a timing issue in deployment process overview page which was causing intermittent failures

Changes in Octopus 2019.8.6

  • 5797 - Fixed how manual interventions are handled when they occur during a deploy release step
  • 5835 - Account parameters used in Step Templates are now expanded, making them easier to use
  • 5851 - Shows cleaner exception message when executable is not found in steps with script logic
  • 5866 - Fixed an issue that caused certain steps to now show in the channel version rule selector
  • 5868 - Fixed comparison of package ids between build information and steps to be case insensitive
  • 5872 - Improved validation and error messsages for Automatic Release Creation package steps
  • 5874 - Improve reliability of temp file handling on Linux targets and avoid silent failure of "Deploy to NGINX" steps
  • 5878 - Removed duplicate email validation when modifying or registering users

Changes in Octopus 2019.9.0

  • 5755 - Added informational message on how to work around PowerShell terminating processes on Win2019 and .NET 4.7.2 when an error is output
  • 5824 - Project logos are now copied when a project is cloned
  • 5880 - helm init in the Helm Upgrade step no longer refreshes the local repository cache
  • 5883 - Fix for Kubernetes node affinity not being set during deployment
  • 5889 - Project overview screen is no longer dependant on LibraryVariableSetView permission for Tenanted projects

Changes in Octopus 2019.9.1

  • 5894 - Create User action can now add external logins, due to a bug was only available in editing existing users
  • 5896 - Fixes rare crash in editing a package deployment step if a large amount of feeds are present

Changes in Octopus 2019.9.2

  • 5901 - Fix for upgrade error unable to find id in Script0206 - affecting case sensitive SQL server instllations

Changes in Octopus 2019.9.3

  • 5905 - Fixed an issue where a project was not able to be cloned when the logo file was missing, the cloned project will now use the default logo

Changes in Octopus 2019.9.4

  • 5921 - UI performance boost for Octopus instances with lots of projects doing lots of deployments
  • 5922 - Fix for duplicate key exception when cleaning up build information/package metadata
  • 5929 - Fix for StackOverflowException causing Octopus Server to crash
  • 5930 - Fix for recursive variable loop when there isn't one

Changes in Octopus 2019.9.5

  • 5957 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages - CVE: CVE-2019-19084
  • 5960 - Fixed a stored cross-site-scripting (XSS) vulnerability - CVE: CVE-2019-19085

Changes in Octopus 2019.9.6

  • 5965 - Upgraded Let's Encrypt support to ACME v2

Changes in Octopus 2019.9.7

  • 5983 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages on Octopus Cloud - CVE: CVE-2019-19084
  • 5984 - Changed machine license check to sql column for better performance

Changes in Octopus 2019.9.8

  • 5997 - CSRF cookie sometimes missing secure attribute - CVE: CVE-2019-19375
  • 6001 - Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
  • 6004 - Invalid request submitted to Team API can cause denial of service - CVE: CVE-2019-19376

Changes in Octopus 2019.9.9

  • 6009 - Fix issue where project switcher would open a new tab when clicking away
  • 6018 - Fixed a bug with GitHub feed tags not getting more than the first 100 tags
  • 6022 - UI rendering performance improvements to the projects list screen for customers operating at scale

Changes in Octopus 2019.9.10

  • 6028 - Fixed a bug where connections may have been opened unnecessarily when querying the /api/projects/all endpoint

Changes in Octopus 2019.9.11

  • 6053 - Added retries running the Tentacle MSI to the Tentacle upgrader if msiexec failed to run successfully
  • 6078 - Enhanced logging of timezone conversion failures during scheduled health checks
  • 6082 - Fixed a bug where deleting a parent step might delete the wrong step

Changes in Octopus 2019.9.12

  • 6088 - Fix React Error in container within Kubernetes step

Changes in Octopus 2019.9.13

  • 6096 - Enabled issue trackers to use the web proxy configured in Octopus

Changes in Octopus 2019.9.14

  • 6229 - Fixed bug where Octopus was ignoring proxy config when configuring Azure targets

Changes in Octopus 2019.9.15

  • 6254 - On premise Active Directory privilege escalation bug fixed

Changes in Octopus 2019.10.0

  • 4270 - Allow deferring the package selection until the step template is added to a project
  • 5601 - Release filter dropdown will now show a few options when clicked on
  • 5604 - Added a new deployment variable for changes, and a Deployment Notes template on the project settings to control its content
  • 5606 - Build Information search and view added to the Library
  • 5848 - "Stop a Docker Resource" step will not remove the containers unless "Stop and remove" action is explicitly selected
  • 5860 - Package selection dropdown will now show a few options when clicked on
  • 5881 - Adds support for PowerShell Core deployment scripts on all platforms. Breaking Change: PowerShell scripts (for example, .ps1 files embedded in packages) will be run on non-windows targets
  • 5885 - Package Metadata renamed to Build Information (Branch is now included too)
  • 5886 - Fixed bug with child project version comparisons during release creation
  • 5888 - Introducing Runbooks for Operations Teams (EAP feature)
  • 5893 - Create User action can now add external logins, due to a bug was only available in editing existing users
  • 5895 - Fixes rare crash in editing a package deployment step if a large amount of feeds are present
  • 5900 - Fix for upgrade error unable to find id in Script0206 - affecting case sensitive SQL server installations
  • 5903 - Fixed an issue where a project was not able to be cloned when the logo file was missing, the cloned project will now use the default logo

Changes in Octopus 2019.10.1

  • 5892 - Fix for duplicate key exception when cleaning up build information/package metadata
  • 5897 - UI performance boost for Octopus instances with lots of projects doing lots of deployments
  • 5899 - On the project process view, the step list overlaps if the step name has long words
  • 5912 - Fix issue where project switcher would open a new tab when clicking away
  • 5913 - Fixed issue with Build Information upgrade script that would block if it couldn't find expected old indexes
  • 5917 - UI rendering performance improvements to the projects list screen for customers operating at scale
  • 5918 - Fix for handling of deployment processes where a null package collection may result in a Value cannot be null error during deployment
  • 5919 - Fix an issue where adding a project group would result in an empty page being shown

Changes in Octopus 2019.10.2

  • 5802 - Enforce version checks for Octopus.Migrator
  • 5923 - OpenID Connect authentication provider packaging updated
  • 5924 - Fix for StackOverflowException causing Octopus Server to crash
  • 5927 - Fix for recursive variable loop when there isn't one
  • 5931 - Fix task screen crashing when viewings tasks unrelated to deployments and runbooks
  • 5933 - UI option to load a sample process for new projects
  • 5935 - "Missing Resource" chip no longer displaying on Machine Clean Up Events page
  • 5936 - Lowered the severity of some messages logged by Halibut when client connections timeout
  • 5937 - Fixed tenant scoping issue with the DeploymentView permission, which would prevent all deployments from appearing on the dashboard
  • 5939 - Fixed bad data for release versions in package metadata
  • 5940 - Prevent modification of some of the user roles for Octopus Administrators and Octopus Managers

Changes in Octopus 2019.10.3

  • 5902 - Upgraded Let's Encrypt support to ACME v2
  • 5928 - Prevented Azure DevOps connectivity issues blocking access to the package library
  • 5938 - Health Check tasks not associated with a Machine Policy are now deleted after 30 days
  • 5941 - Deploy Kubernetes Containers step now creates deployment resources using the apps/v1 API
  • 5947 - Better project switcher - shows recently viewed projects and uses server-side filtering
  • 5948 - Fixed a UI bug causing confirmations to display "e.props.dialogOnClose is not a function"
  • 5952 - Adding Migrator support for Runbooks
  • 5954 - Error when disabling automatic release creation

Changes in Octopus 2019.10.4

  • 5887 - Updated external security group check against AD to prevent hanging task
  • 5943 - Fixed an error calling octo create-release when package version supplied for a deploy a release step does not exist
  • 5944 - Changed machine license check to sql column for better performance
  • 5950 - Added log warning in Calamari when it detects Management Certificates in use on an Azure Web App step
  • 5951 - Improved Let's Encrypt problem explanations with details of the remote status
  • 5958 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages - CVE: CVE-2019-19084
  • 5961 - Fixed a stored cross-site-scripting (XSS) vulnerability - CVE: CVE-2019-19085

Changes in Octopus 2019.10.5

  • 5925 - Added DeployedBy to the /api/deployments/{id} api call
  • 5946 - Fixed a rare edge case in retrying failed deployments to an environment after the lifecycle was modified
  • 5955 - Improved the error message shown when a corrupt certificate is detected
  • 5963 - Validate that deployment target roles don't contain | characters
  • 5964 - Fixes Add Trigger dropdown button does not close and steals focus
  • 5968 - Added AzureRM aliasing to fix missing commands issue
  • 5971 - Fixed an information disclosure vulnerability during error handling of maliciously crafted packages on Octopus Cloud - CVE: CVE-2019-19084
  • 5972 - Restored the project overview to use the full width of the screen
  • 5979 - Fixed an issue with the Kubernetes step not correctly quoting label values
  • 5980 - Fixed uploading packages errors with - contains invalid characters

Changes in Octopus 2019.10.6

  • 5978 - Fixed issue with S3 filenames converting spaces to %20
  • 5985 - Fix handling of empty LifecycleIds when saving Channels
  • 5986 - Multi-select drop down will now position itself correctly when it is opened at the bottom of the screen
  • 5987 - Disabled the New API Key button when viewing another users account
  • 5988 - Allow Octo to run on .NET Core 3 and above
  • 5990 - Adding Offline Drop Targets support for Runbooks
  • 5991 - Adding Runbook filtering to the Tasks screen
  • 5992 - Adding ability to update variable snapshots for Runbooks
  • 5993 - Fixed a bug where a deployment might not deploy where you expect if the deployment preview has not finished loading
  • 5995 - Runbooks Overview and List screen design updates
  • 6005 - Invalid request submitted to Team API can cause denial of service - CVE: CVE-2019-19376

Changes in Octopus 2019.10.7

  • 5974 - Fix bug where the file chooser doesn't open when replacing certificates
  • 5998 - CSRF cookie sometimes missing secure attribute - CVE: CVE-2019-19375
  • 5999 - Fixed an JavaScript undefined error when adding a service port in a K8S deployment
  • 6002 - Adding Tasks menus for Projects, Tenants and Runbooks
  • 6006 - Fixed bug in project switcher when user has recently viewed a now inaccessible project
  • 6007 - Fixed deployment preview UI when release changes is empty

Changes in Octopus 2019.10.8

  • 5173 - Included Azure CLI tools when deploying to Kubernetes with Azure credentials
  • 5989 - Allow configuring pod service account in deploy k8s containers step
  • 5994 - Improved tenanted deployment preview screen to batch API calls which improves performance
  • 6011 - Deferred deployments are now taken into account on the project and main dashboards
  • 6012 - Allow variables to be set for tentacle health checks
  • 6013 - Show a preview of the release notes on the deployment page with a button to show more
  • 6014 - Aligned the retention of non-deployment and non-health check tasks to be the last 20 and the last 30 days
  • 6017 - Fixed a bug with GitHub feed tags not getting more than the first 100 tags
  • 6019 - Fixed issue where the Azure PowerShell modules weren't configured correctly when deploying a helm chart to Azure AKS

Changes in Octopus 2019.10.9

  • 4559 - Fixed bug causing new targets to not be included in deployments when targets are re-included by the same health check
  • 5945 - Update the Jira Issue Tracker test button to do a more thorough check of the user's permissions and ability to read work items
  • 6010 - Fixed race condition when selecting tenants or tags when creating a release possibly causing the wrong deployment to be shown
  • 6015 - Added a UriPart function to Octostache
  • 6023 - Fixed issue in health checks where machines were not correctly re-included into the deployment
  • 6024 - The Deployments and Operations menus within a project now always remain open
  • 6025 - Fixed bug that was excluding targets from deployments if they were "healthy with warnings"
  • 6026 - Fixed dropdown "select as you type" functionality
  • 6027 - Fixed a bug where connections may have been opened unnecessarily when querying the /api/projects/all endpoint
  • 6031 - Fixed a regression with force package deployment that was introduced in 2019.10

Changes in Octopus 2019.10.10

  • 6036 - Option to not re-deploy release for scheduled trigger with "deploy latest release" action
  • 6042 - Fix on screen error for channel creation

Changes in Octopus 2019.10.11

  • 3765 - The start time for targets in rolling deployments is now shown correctly in the log headers
  • 6035 - Reduce network IO usage in Windows listening tentacles
  • 6037 - Fixed db query to improve speed of task event query

Changes in Octopus 2019.10.12

  • 5554 - Support for Self-Hosted BitBucket commit links
  • 5942 - Improved the formatting of BitBucket commit link urls
  • 6029 - Fixed json configs not replacing variables that start with "octopus"
  • 6032 - Fixed error messaging showing when updating a project from a step template that has been changed to use a package type variable
  • 6038 - Fixed error that cause an Object refrence not set error to show on the package search
  • 6044 - Added retries running the Tentacle MSI to the Tentacle upgrader if msiexec failed to run successfully
  • 6046 - Added support for using Set-PSDebug -trace to diagnose PowerShell errors
  • 6047 - Improved PowerShell error messages when exceptions occur
  • 6050 - Fixed an obscure error with Kubernetes health checks on windows 2019
  • 6051 - Fix bug where health checks would not re-include targets under certain conditions

Changes in Octopus 2019.11.0

  • 4728 - Health Check and Tentacle Upgrades work with filters
  • 4925 - Breaking change Restructured scheduled triggers and fixed bug where scheduled trigger was missing intervals
  • 5843 - Fixed links to manual intervention in the audit log and task history
  • 5861 - Filtering Dashboard by Max Limit does not add errors or warnings
  • 5977 - Added prompted variable support for runbooks by allowing variables to be scoped to both deployment and runbook processes
  • 6034 - Introducing Publishing for Runbooks
  • 6039 - Reliably show package acquisition location radio buttons
  • 6043 - UI adding Triggers menus for Runbooks
  • 6052 - Show additional information in Tentacle and Server Manager when checking for the presence of PowerShell 2.0 fails
  • 6055 - Octopus Client checks now whether the package upload was successful when the upload times out
  • 6056 - Fixed bug where links in the audit log for modifications to accounts pointed to /app/#not-found instead of the account
  • 6057 - Add runbook usages for accounts, library variable sets and script modules
  • 6059 - Fixed bug in Tentacle where Powershell wasn't being checked if it was installed correctly

Changes in Octopus 2019.11.1

  • 6054 - Fix bug causing deployments to target incorrect environments when slow to return preview data
  • 6063 - Fixes bug that makes select dropdown unclickable
  • 6064 - Add "Test" button for Azure DevOps Issue Tracker connectivity in settings
  • 6065 - Fix bug causing some server tasks to not be cleaned up correctly
  • 6068 - Added a re-deploy button to the deployment page
  • 6069 - Fixed bug where links in the audit log for modifications to user roles pointed to /app/#not-found instead of the role
  • 6070 - Improve logging of timezone conversion failures during scheduled health checks
  • 6071 - Fixed issue with filtering of environments and worker pools collapsing groups when removing a filter
  • 6072 - Fix bug where upgrading instances with runbooks would always show false warnings

Changes in Octopus 2019.11.2

  • 4440 - Include experimental support for linux-arm SSH targets
  • 5687 - Newline characters in variables are persisted after editing
  • 5822 - Cancelling a health check for an offline Tentacle now cancels much quicker, and no longer waits the full connect timeout
  • 5840 - Fixed a bug where deleting a parent step might delete the wrong step
  • 6060 - Update UI to Show Spaces dropdown when permitted to add spaces or has access to multiple spaces
  • 6066 - Improved performance for many places using projects, including the projects page and the tasks page
  • 6081 - Handled trailing semicolons in the address field of the send email step
  • 6085 - Fixed issue where sometimes server tasks are not processed until restart

Changes in Octopus 2019.11.3

  • 5769 - Disable adding a new project in the UI when there are no Project Groups or Lifecycles
  • 6061 - The target limit specified in the license is enforced now
  • 6073 - Fix React Error in container within Kubernetes step
  • 6083 - External groups are now indicated on users' teams lists
  • 6086 - Fixed layout issue on the User Role tab on the Team Edit page

Changes in Octopus 2019.12.0

This LTS roll up release includes all bug fixes and features up until 2019.11.3

  • 5769 - Disable adding a new project in the UI when there are no Project Groups or Lifecycles
  • 6061 - The target limit specified in the license is enforced now
  • 6073 - Fix React Error in container within Kubernetes step
  • 6083 - External groups are now indicated on users' teams lists
  • 6086 - Fixed layout issue on the User Role tab on the Team Edit page

Changes in Octopus 2019.12.1

  • 6124 - Scheduled triggers for Operations Runbooks that have prompted variables no longer throw a NullReferenceException
  • 6129 - Drop experimental header check on project/summaries to avoid issues with proxies
  • 6131 - Fix an issue where Octopus Server would user the tar extractor for tar.gz resulting in Bad GZIP header error messages
  • 6132 - Download helm charts directly from a helm repository instead of relying on the helm executable

Changes in Octopus 2019.12.2

  • 6144 - Support Helm V3
  • 6438 - Fixed potential leakage of feed password into deployment log CVE-2020-14470

Changes in Octopus 2019.12.3

  • 6169 - Improved swagger documentation to ensure parameters match the path more accurately
  • 6170 - External group/role chips for teams now show ids on hover
  • 6171 - Fixed layout issue on Usage tab for Library Variable Sets, Lifecycles and Script Modules
  • 6172 - Corrected swagger operationid's to be unique
  • 6173 - Enabled issue trackers to use the web proxy configured in Octopus
  • 6174 - Fixed issue where sensitive step parameters were cleared when updating step template in a deployment process
  • 6175 - Clear sensitive variable values when re-running a step template run so it doesn't look like the value is set
  • 6176 - Issue tracker connectivity tests can now execute even when the extension itself is disabled
  • 6177 - TFVC ChangeSets are now rendered as links in the Build information
  • 6178 - Improved responsiveness of the tenants list screen with missing variables
  • 6181 - Fix issue where variables page would crash at certain screen sizes

Changes in Octopus 2019.12.4

  • 6188 - Fix DateTime overflow and year skip in db upgrade schedule conversion

Changes in Octopus 2019.12.5

  • 6201 - Fixed an issue where pushing a package results in a SQL timeout if you have many large deployment processes

Changes in Octopus 2019.12.6

  • 6208 - Respect the path component of the docker feed's Registry Path when calling docker pull
  • 6213 - Migrator's partial export now supports export of Runbook snapshots

Changes in Octopus 2019.12.7

  • 6230 - Fixed bug where Octopus was ignoring proxy config when configuring Azure targets
  • 6231 - Fixed bug where the proxyUri PowerShell variable was interfering with user defined variables
  • 6236 - Fixed bug where the deprecated package variables like 'NugetPackageId' weren't populated
  • 6237 - Fix bug where it can sometimes be slow to retrieve tenant variables
  • 6243 - Fixed bug where a Runbook couldn't be published

Changes in Octopus 2019.12.8

  • 6255 - On premise Active Directory privilege escalation bug fixed

Changes in Octopus 2019.12.9

  • 6331 - TaskView permission is not scoped to any dimensions e.g. Projects, environments and tenants (CVE-2020-12286)

Changes in Octopus 2019.12.10

  • 6309 - Runbook task status can only be updated when user has RunbookRunCreate permission (CVE-2020-12482)

Changes in Octopus 2019.12.11

  • 6345 - EventViewPermission is not scoped correctly if there are multiple values in any single dimension

Changes in Octopus 2019.12.12

  • 6349 - Octopus Server doesn't send azure authentication traffic through webproxy

Changes in Octopus 2019.12.13

  • 6407 - Prevent SQL Timeouts crashing the Releases and Tasks Page for users with complex permissions

Changes in Octopus 2019.12.14

  • 6416 - Adjusted security to allow downloads in Chrome 83

Changes in Octopus 2019.13.0

  • 5911 - Auto deploy processing has significantly changed to prevent cases where machines are missed
  • 6076 - Fixed issue where sensitive step parameters were cleared when updating step template in a deployment process
  • 6089 - Clear sensitive variable values when re-running a step template run so it doesn't look like the value is set
  • 6090 - External group/role chips for teams now show ids on hover
  • 6091 - Improved swagger documentation to ensure parameters match the path more accurately
  • 6092 - Updated AWS SDK S3 to 3.3.110.10 within Calamari (v8.1.4)
  • 6094 - Fixed layout issue on Usage tab for Library Variable Sets, Lifecycles and Script Modules
  • 6095 - Enabled issue trackers to use the web proxy configured in Octopus
  • 6097 - Issue tracker connectivity tests can now execute even when the extension itself is disabled
  • 6098 - Corrected swagger operationid's to be unique
  • 6100 - Added extra validation for the variables supplied as part of a Script Module
  • 6101 - TFVC ChangeSets are now rendered as links in the Build information
  • 6103 - Improved swagger documentation

Changes in Octopus 2019.13.1

  • 5770 - Fix for dialog issue in Firefox/Edge with the Kubernetes step template
  • 6099 - Resolved issue preventing k8s raw yaml volume from being saved if it contained a variable expression
  • 6104 - Fix to consider both release and runbook snapshots before deleting the shared variable set snapshot
  • 6112 - Fixing runbook run and snapshot variable links to match the UI redirection logic
  • 6116 - Scheduled triggers for Operations Runbooks that have prompted variables no longer throw a NullReferenceException
  • 6117 - Scheduled deployments and runbook runs will now use default prompted variable values
  • 6118 - Stop icons shrinking in Team lists when the name/description is long
  • 6121 - "An item with the same key has already been added" error with the NGINX step and multiple regex based locations
  • 6126 - Drop experimental header check on project/summaries to avoid issues with proxies

Changes in Octopus 2019.13.2

  • 5543 - Download helm charts directly from a helm repository instead of relying on the helm executable
  • 6133 - Changed Releases screen so it doesn't go boom if your instance/space doesn't have any environments
  • 6134 - Reduce likelihood of dashboard queries timing out
  • 6136 - Fix for user lockout when exceeding limit of wrong password attempts
  • 6137 - Package IDs with slashes break the NGINX step by placing conf files in a subdirectory

Changes in Octopus 2019.13.3

  • 6140 - Fix for a blocking TypeScript error occurring in IE11

Changes in Octopus 2019.13.4

  • 6141 - Fixes bug where colors aren't show in IE11
  • 5953 - Web Request proxy not detecting bypass list

Changes in Octopus 2019.13.5

  • 5909 - Ensure Tenant Variables are cleaned up when Tenants are deleted
  • 6048 - Support Helm V3
  • 6120 - Fix an S3 step issue where uploading a package using the filename differs between the built-in and external workers
  • 6125 - Fix issue where variables page would crash at certain screen sizes
  • 6138 - Adding runbook variables (Id, Name) to the list of contributed variables during a run
  • 6147 - Fix for API bug where certain index responders could not filter by ids
  • 6153 - Improved validation on IIS bindings property when supplied with unexpected data
  • 6154 - Improved responsiveness of the tenants list screen with missing variables
  • 6155 - Fix to stop 'no auth providers' text flashing on the sign-in page
  • 6159 - Run Script step will now include script name and arguments in the process overview as part of the summary when configured to use a script from a package
  • 6160 - Improved the performance and UX of the project switcher for customers operating at scale

Changes in Octopus 2019.13.6

  • 6102 - Fixing import migrations for multiple project triggers and runbooks
  • 6135 - Fixed issue preventing Azure DevOps Issue Tracker to be enabled on Octopus Cloud
  • 6157 - Fix icon alignment for copy API key button
  • 6180 - Fix a race condition on the runbook run page which was causing previews to get out of sync
  • 6184 - Fixed bug where package extraction is failing on OSX and BSD targets

Changes in Octopus 2019.13.7

  • 6143 - Fix to the variables/all endpoint when runbooks are in use
  • 6152 - Fix DateTime overflow and year skip in db upgrade schedule conversion
  • 6164 - Fixed up the messages printed in the summary section of health checks
  • 6186 - UI will now default to the last accessed space when no explicit space is provided

Changes in Octopus 2020.1.0

  • 5842 - The Worker Pool used by a step can now be varied by environment, tenant or tag via project variables
  • 6139 - Run AWS CLI script, AWS S3 Upload and AWS CloudFormation steps can now run on Linux workers
  • 6190 - Pre-fill database name field with recommended name in Octopus Server setup wizard
  • 6192 - Enable Dark Theme
  • 6193 - Added the ability to extend the web portal's functionality dynamically
  • 6194 - Octopus uses now as few MARS connections as possible which significantly improves performance on Linux

Changes in Octopus 2020.1.1

  • 6150 - A package referenced by a Runbook is not deleted by retention policy
  • 6166 - Package extraction now works on the first try when deploying to Mac via SSH
  • 6189 - Downloading package from built-in library will now have content length headers set
  • 6199 - Handle two-part extensions like "tar.gz" when parsing file names
  • 6200 - Fixed an issue where pushing a package results in a SQL timeout if you have many large deployment processes
  • 6207 - Respect the path component of the docker feed's Registry Path when calling docker pull
  • 6210 - Migrator's partial export now supports export of Runbook snapshots
  • 6216 - NGINX step now defaults to creating config files with tenant, environment and package id in the file name
  • 6222 - Allow Azure script and ARM template steps to run on Linux workers
  • 6223 - Allow using Azure service principal or AWS account authentication for Kubernetes on Linux workers

Changes in Octopus 2020.1.2

  • 3591 - Library Variable Set View and Edit permissions now support Tenant and Environment scoping. They are no longer coupled to EnvironmentView
  • 6058 - Fixed bug where Octopus was ignoring proxy config when configuring Azure targets
  • 6142 - Fixed bug where multiple directives in NGINX step where getting overridden
  • 6218 - Resolved an issue that prevented a limited number of Octopus Cloud customers from running tasks on the built in worker

Changes in Octopus 2020.1.3

  • 6238 - Fix bug where it can sometimes be slow to retrieve tenant variables
  • 6240 - Don't display pre-release packages by default when selecting specific versions for release
  • 6241 - Fixed bug where the deprecated package variables like 'NugetPackageId' weren't populated
  • 6244 - Fixed bug where a Runbook couldn't be published

Changes in Octopus 2020.1.4

  • 6256 - Fixed a bug where we were shipping a .NETCore version of Octopus.Client, which would break "run on server" scripts that were loading the client dll in PowerShell

Changes in Octopus 2020.1.5

  • 6258 - On premise Active Directory privilege escalation bug fixed
  • 6260 - Tentacle upgrade button is displayed again
  • 6261 - Using a Deploy Package step works again when targeting one of the deprecated Azure Web App targets

Changes in Octopus 2020.1.6

  • 6204 - Fixed bug where the proxyUri PowerShell variable was interfering with user defined variables
  • 6283 - Fix bug with auto-upgrade of tarball Linux tentacles
  • 6262 - Fix connectivity issue with older polling tentacles
  • 6266 - Fix connectivity issue with Listening Tentacles when the Octopus Server is using an SHA1 certificate

Changes in Octopus 2020.1.7

  • 6267 - Rather than running all packaged scripts for a hook, run just one based on OS preferences
  • 6273 - Redirect user to sign-in form if integrated sign-in fails

Changes in Octopus 2020.1.8

  • 6275 - Fix bug where Java-based deployments failed on non-Windows targets
  • 6280 - Fix bug where you can't download plain text artifacts greater than 4KB in size

Changes in Octopus 2020.1.9

  • 6287 - Fixed a bug where server would crash writing to the server log on Linux

Changes in Octopus 2020.1.10

  • 6278 - Fix bug where the Tenant Common Variable Tab is missing when LibraryVariableSetView permissions are scoped to a Tenant or Environment
  • 6281 - Fixed error with upgrading from 2018 versions to 2020.1
  • 6289 - Maven artifacts are properly selected when creating a release with channel rules

Changes in Octopus 2020.1.11

  • 6295 - Email notification fonts corrected for outlook
  • 6296 - Fix bug where workers from a second pool might not be released if the default pool is a dynamic worker pool
  • 6299 - Clean up a tenants runbook runs when they are deleted
  • 6302 - Fixes a performance issue in deployment creation when involving a large number of steps, parameters, and tenancies
  • 6306 - Extended the default health check interval in machine policies from 1 hour to 1 day
  • 6307 - Fixes an error that prevented disabling run steps on Octopus Server

Changes in Octopus 2020.1.12

  • 6310 - Runbook task status can only be updated when user has RunbookRunCreate permission (CVE-2020-12482)
  • 6332 - TaskView permission is not scoped to any dimensions e.g. Projects, environments and tenants (CVE-2020-12286)

Changes in Octopus 2020.1.13

  • 6311 - Removed Release Lane and Long-Term Support concepts from Octopus Server - every release from 2020.1 comes with 6 months support
  • 6313 - Fixes a UI error when creating a scheduled trigger
  • 6315 - Fixes an issue where a run condition based on a variable expression doesn't work when the variable is scoped to a process
  • 6319 - SynchronizeExternalSecurityGroupsForUsers task is not executed when AD integration is not present

Changes in Octopus 2020.1.14

  • 6346 - EventViewPermission is not scoped correctly if there are multiple values in any single dimension

Changes in Octopus 2020.1.15

  • 6325 - Fixes an issue where deploying a package to an Azure Cloud Service target would result in an infinite loop during deployment
  • 6328 - Added "Audit Trail" option to overflow menu for spaces

Changes in Octopus 2020.1.16

  • 6265 - Fixes integrated authentication headers when using active directory integration
  • 6341 - Fixes an issue with Deploy a Release step where deployment would fail if release contained a Manual Intervention step
  • 6342 - SonaType Nexus Helm repo as an external feed no longer errors
  • 6343 - Fixes an issue where active directory groups were not synchronizing correctly for some users
  • 6350 - Fixes an issue where Azure logins were not being correctly proxied

Changes in Octopus 2020.1.17

  • 6358 - Fixes HTTP protocol errors with 304 Not Modified

Changes in Octopus 2020.1.18

  • 6373 - Fixed cloned tenants not being editable if the tenant they were cloned from got deleted
  • 6375 - Fixed Package Feed variable not found Error in the UI

Changes in Octopus 2020.1.19

  • 6408 - Prevent SQL Timeouts crashing the Releases and Tasks Page for users with complex permissions

Changes in Octopus 2020.1.20

  • 6415 - Adjusted security to allow downloads in Chrome 83

Changes in Octopus 2020.1.21

  • 6441 - Fixed API endpoint for projects/expirmental/summaries not being encoded correctly

Changes in Octopus 2020.1.22

  • 6531 - Breaking change Certificates and accounts used by deployment targets must now be scoped to all tenants the deployment target belongs to - CVE: CVE-2020-16197

Changes in Octopus 2020.2.1

  • 6275 - Fix bug where Java-based deployments failed on non-Windows targets
  • 6276 - Fix bug where you can't download plain text artifacts greater than 4KB in size

Changes in Octopus 2020.2.2

  • 6263 - Added a system variable with the date and time the Release currently being deployed was created
  • 6285 - Fix - Navigating to an unavailable project now handles error gracefully

Changes in Octopus 2020.2.3

  • 6245 - Fix bug where workers from a second pool might not be released if the default pool is a dynamic worker pool
  • 6250 - Improved performance of tenant variables page when multiple Certificate variables are displayed
  • 6290 - Fixed package acquisition failure when target is found that needs the same package already planned for an existing target
  • 6291 - Clean up a tenants runbook runs when they are deleted
  • 6294 - Fixes an error that prevented disabling run steps on Octopus Server
  • 6301 - Fixes a performance issue in deployment creation when involving a large number of steps, parameters, and tenancies
  • 6305 - Extended the default health check interval in machine policies from 1 hour to 1 day
  • 6312 - Runbook task status can only be updated when user has RunbookRunCreate permission (CVE-2020-12482)

Changes in Octopus 2020.2.4

  • 3206 - Adding variable run conditions for child steps
  • 5898 - Fixes an issue with Deploy a Release step where deployment would fail if release contained a Manual Intervention step
  • 6259 - Added a migration script to modify any DeploymentProcess records that reference empty TenantId's to use NULL's instead
  • 6318 - Allow Kubernetes steps to import and export YAML
  • 6320 - Octopus Server requires SQL Server 2017 or newer
  • 6323 - Kubernetes steps can now be used within runbooks
  • 6329 - Code editor in fullscreen is now displaying the correct syntax highlighting
  • 6330 - Execution Containers for Workers - Steps that run on a worker can specify a container to execute the step in
  • 6334 - Removes release notes template from Runbook publishing notes
  • 6338 - Duplicate html on Octopus Deploy loading screen complicates loading
  • 6339 - Added ability to configure tolerations on deploy k8s containers step
  • 6340 - Inline variables insert for code editors
  • 6344 - Fixes an issue where active directory groups were not synchronizing correctly for some users

Changes in Octopus 2020.2.5

  • 6352 - SonaType Nexus Helm repo as an external feed no longer errors
  • 6354 - Added the X-Robots-Tag header so that Google won't index Octopus instances
  • 6362 - Fixes HTTP protocol errors with 304 Not Modified

Changes in Octopus 2020.2.6

  • 6361 - Upgrading a Linux Tentacle no longer updates all system packages
  • 6365 - Fixed Script Step doesn’t run on Targets when Workers available

Changes in Octopus 2020.2.7

  • 6367 - Fix for parent step variable run conditions

Changes in Octopus 2020.2.8

  • 6219 - Fixed cloned tenants not being editable if the tenant they were cloned from got deleted
  • 6269 - Package feed variable not found error displayed in the UI
  • 6372 - Fixed tasks stuck after cloud node re-provisioning (eg Manual Interventions)
  • 6378 - Skip inaccessible certificate stores when deploying HTTPS bindings to an IIS website
  • 6379 - Prevent Docker login warning from causing deployments to fail on Windows

Changes in Octopus 2020.2.9

  • 6381 - Helm chart versions are now sorted for repositories that don't return data in version order

Changes in Octopus 2020.2.10

  • 6387 - Fix to support object parameter default values in ARM templates entered as JSON
  • 6395 - The SQL Server compatibility level will be raised automatically to 140 to match SQL Server 2017

Changes in Octopus 2020.2.11

  • 6397 - X-Forwarded-For field included in web logs
  • 6402 - Containers are now cleaned up after an Action Container Image finishes running

Changes in Octopus 2020.2.12

  • 6406 - Fixed a bug where expandable sections were incorrectly collapsed by default when creating new resources
  • 6409 - Prevent SQL Timeouts crashing the Releases and Tasks Page for users with complex permissions

Changes in Octopus 2020.2.13

  • 6414 - Adjusted security to allow downloads in Chrome 83
  • 6417 - Added ability to limit the size of the cache directory

Changes in Octopus 2020.2.14

  • 6410 - Added telemetry that gathers and aggregates the duration of API and database calls and sends them for analysis
  • 6431 - Fixed a bug where packageId variables could not be scoped to a process

Changes in Octopus 2020.2.15

  • 6418 - Added an option to configure the shared cluster directory so that the package store, task logs and artifacts directories don't need to be configured individually
  • 6447 - Changed the format of the Telemetry file to be more space efficient. Added a command line option to set the path of the telemetry logs
  • 6452 - Added always run pre scripts to update database compatibility version to 140 even if there's no new migrations