Compare releases

Compare releases and check for compatibility between your existing Octopus Server and new releases.

→

What's new

These are the most important features you'll get by upgrading from 2019.12.8 to 2020.3.4

Octopus 2020.3

Highlights

Customer-driven runbook improvements, Jenkins Pipelines support, streamlined process editor and early access to our Octopus Linux Docker image.

  • Runbooks improvements: This release includes a batch of customer-driven improvements, including runbook-only projects, Octopus CLI support, environment scoping, guided failure mode per runbook, and the addition of runbook retention policies.
  • Jenkins Pipelines support enables you to integrate with Octopus from your Jenkinsfile.
  • Streamlined process editor allows you to edit multiple steps at once and save your changes with a single update.
  • Octopus Linux Docker image (Early access) is now available, making it possible to run Octopus in a Linux Docker container.

Read our blog post to learn more.

Breaking changes

This release includes two breaking changes:

  • Deprecated our Azure VM extensions - We recommend using PowerShell DSC as a replacement. Our documentation covers this decision and links to further articles on how to achieve this with PowerShell DSC. See this article for instructions to accomplish this with Amazon Web Services as well.
  • Updated Deploy to IIS step - We have updated this step to remove support to deploy to Azure App Services. We recommend using our Azure support instead.

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/

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 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 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.

Release notes

These are the features and fixes you'll get by upgrading from 2019.12.8 to 2020.3.4.

Changes in Octopus Server 2020.3.4

  • 6490 - UI fixes to get publishing buttons showing in the primary Runbook layouts
  • 6520 - UI fix to show step information in deployment preview
  • 6534 - UI fixing expanders in step editor and library variable sets
  • 6543 - Fix server task log files being left open
  • 6563 - Fix bug where certain passwords are written to the deployment log in plain-text - CVE: CVE-2020-24566

Changes in Octopus Server 2020.3.3

  • 6529 - 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
  • 6321 - Accounts can now be selected without refreshing on the tenant common variables screen
  • 6500 - Default variables are displayed again on tenant variable selection screens
  • 6509 - fixes issue that prevented worker pools being selectable for deployment targets
  • 6512 - Octopus Server service will keep running when version control project's background sync throws an SQL timeout exception
  • 6507 - Fix regression in Octopus Server Manager to allow using an existing database if the master-key is known

Changes in Octopus Server 2020.3.2

  • 5862 - Fix filter alignment on multiple pages
  • 6485 - Fixes to include the CORS headers and any custom cookie domain to the integrated-challenge endpoint response
  • 6491 - Azure accounts scoped to tenanted and untenanted deployment mode are validated correctly for untenanted deployments
  • 6515 - Fixed the Download as JSON menu item for runbooks

Changes in Octopus Server 2020.3.1

  • 5691 - Fixed an issue where worker pool selection reset to default when changing execution location
  • 6080 - Removes an incorrect note when setting sensitive fields in tenant variables
  • 6182 - Fixed an issue where the Kubernetes Container Step wasn't allowing Variables for the "Volume Name"
  • 6252 - Fixed a bug where packageId variables could not be scoped to a process
  • 6277 - Pre-releases now correctly show the current release changes only
  • 6336 - Adds variable to set a non-default Azure CLI Extensions Folder
  • 6348 - Maven artifacts can optionally be specified by packaging and classifier, for example org.example:myartifact:jar, org.example:myartifact:zip or org.example:myartifact:jar:sources
  • 6355 - Helm charts can now be stored in the built-in feed
  • 6357 - The task log now changes it's refresh based on the speed of the response and the state of the deployment
  • 6359 - Improved validation on the build information endpoint
  • 6360 - Prevent Docker login warning from causing deployments to fail on Windows
  • 6361 - Upgrading a Linux Tentacle no longer updates all system packages
  • 6363 - Added AccountView permission to built-in Project viewer role
  • 6364 - Fixed Powershell script highlighting
  • 6366 - To prevent potential data corruption, Octopus Server will actively prevent downgrading to an older version before it starts
  • 6368 - Add support for DNS options and termination message in K8S deployment step
  • 6369 - Show a missing resource chip on the Deploy a Release step if the target project is not accessible
  • 6370 - Include more detail on permission exceptions
  • 6374 - Changed the background job scheduler to keep state between nodes and not rely on there being a leader node
  • 6376 - Skip inaccessible certificate stores when deploying HTTPS bindings to an IIS website
  • 6377 - Breaking Change Removed the node Rank (Follower/Leader) and IsLeader
  • 6383 - Added diagnostic logging and verification of files in the Octopus Server directory on launch
  • 6384 - External ID now available when assuming an IAM role
  • 6385 - Azure passwords with leading dash work as expected
  • 6386 - Fix to support object parameter default values in ARM templates entered as JSON
  • 6388 - Prevent SQL Timeouts crashing the Releases and Tasks Page for users with complex permissions
  • 6392 - Upgrade Helm Chart step can now be configured with worker pool
  • 6394 - Fixed generation of Swagger Api Documentation to ensure it's valid according to http://swagger.io|swagger.io
  • 6398 - When using OpenID Connect authentication, ignore unsupported JWKs
  • 6401 - Adjusted security to allow downloads in Chrome 83
  • 6404 - Fixed Library variables are not included in unpublished runbook previews
  • 6405 - Fixed a bug where expandable sections were incorrectly collapsed by default when creating new resources
  • 6420 - UI introducing a multi-step process-editing experience
  • 6423 - Fixed confusing UX when the value for a parameter is empty
  • 6426 - Environment Scoping for Runbooks
  • 6427 - Collapse Deployments / Operations menus in Projects
  • 6428 - Added default guided failure mode to runbook settings
  • 6430 - Added support for specifying the session duration when assuming an AWS role
  • 6432 - Added configurable retention policies for runbooks
  • 6433 - Fixed a bug where Upgrade a Helm Chart Step templates created before 2019.12.2 may be using the wrong helm client version
  • 6436 - Task duration now updates every second
  • 6437 - Fixed rendering of error page
  • 6443 - Added formatting for multiple line commit messages in build information and package pages
  • 6455 - Add support for ingressClassName in Kubernetes Ingress steps
  • 6457 - Fix issue when editing K8S YAML when package is used for project versioning
  • 6458 - Fixed misleading error when creating or upgrading an octopus database using an unsupported version of SQL Server
  • 6461 - Fixed an issue where existing deployment processes with tenant tags caused the UI to error
  • 6462 - Fixed bug where docker image package names weren't being validated correctly when sending build information
  • 6469 - Fixed an issue where the process editor wasn't showing run trigger options
  • 6470 - Fixed an issue where failure run conditions not being shown in process editor
  • 6471 - Fixes an issue where a caller passes an empty string to a tag ID instead of a null and the empty string fails validation
  • 6483 - Reduce storage used by audit events
  • 6484 - Improve view of audit events

Changes in Octopus Server 2020.2.18

  • 6530 - 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 Server 2020.2.17

  • 6492 - Azure accounts scoped to tenanted and untenanted deployment mode are validated correctly for untenanted deployments
  • 6499 - Fixes to include the CORS headers and any custom cookie domain to the integrated-challenge endpoint response

Changes in Octopus Server 2020.2.16

  • 6459 - Fixed misleading error when creating or upgrading an octopus database using an unsupported version of SQL Server

Changes in Octopus Server 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.
  • 6448 - 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

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

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

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

  • 6367 - Fix for parent step variable run conditions

Changes in Octopus Server 2020.2.6

  • 6365 - Fixed Script Step doesn’t run on Targets when Workers available

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

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

Changes in Octopus Server 2020.1.20

  • 6415 - Adjusted security to allow downloads in Chrome 83

Changes in Octopus Server 2020.1.19

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

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

  • 6358 - Fixes HTTP protocol errors with 304 Not Modified

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

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

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

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

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

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

Changes in Octopus Server 2019.13.3

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

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

  • 6416 - Adjusted security to allow downloads in Chrome 83

Changes in Octopus Server 2019.12.13

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

Changes in Octopus Server 2019.12.12

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

Changes in Octopus Server 2019.12.11

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

Changes in Octopus Server 2019.12.10

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

Changes in Octopus Server 2019.12.9

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

Changes in Octopus Server 2019.12.8

  • 6255 - On premise Active Directory privilege escalation bug fixed