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 2018.5.6 to 2019.3.0

Octopus 2018.5

Breaking Changes

We have upgraded the Azure SDK library and the Azure PowerShell modules to support the latest Azure features. Most notably missing was support for nested ARM templates, which will now work out of the box.

These upgrades have also forced the minimum supported environment for Octopus Server to Microsoft .NET 4.5.2 and PowerShell 5.0 so you'll need to plan your upgrade accordingly. The PowerShell 5.0 requirement is only if you are running the Azure PowerShell scripts.

Azure recently announced that from June 30th 2018 they are retiring support for Service Management API (NOTE: Management Certificates use Service Management API). This affects deployments to Azure App Services.

Please switch to using Service Principals for your Octopus Azure accounts

To configure the version of Azure PowerShell modules, we have made a change to the name of the variable. You can now set OctopusUseBundledAzureModules to False.

Octopus 2018.8

Highlights

2018.8.0 introduces initial alpha level support for Kubernetes. These new steps, feeds and targets allow you to deploy Kubernetes Deployment, Service, Ingress, ConfigMap and Secret resources. You can find documentation of these features here.

Client Versions

Octopus.Clients, the Octo CLI command line tools and the Team City plugin must be updated to version 4.39.4 to work with the new features in Octopus 2018.8.0.

CloudFormation

We have added a new feature to the deploy CloudFormation Template step which enables the use of changesets. This allows transforms such as AWS::Serverless and AWS::Include to be used and optionally deferring execution in order to review changes as part of a manual intervention step before executing changes.

Octopus 2018.9

Highlights

Kubernetes

2018.9 removes the alpha feature-flag from the Kubernetes support in Octopus!

The following pieces are now fully-supported members of the Octopus family:

Offline Drop Artifacts

Offline Package Drop targets can now be configured to persist the bundle as an Octopus Artifact.

Offline Package Drop targets could previously only persist the bundle to a file-system directory, which wasn't suitable for Octopus Cloud instances. Artifacts are a perfect fit for this; the deployment bundle is persisted a zip file stored against the deployment in Octopus.

Cloud Dependency Updates

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

  • Azure PowerShell modules upgraded from 5.7.0 to 6.8.1. This update fixes some known issues with the 5.7.0 release of Azure PowerShell.
  • Azure CLI upgraded from 2.0.42 to 2.0.45
  • AWS PowerShell modules upgraded from 3.3.225.1 to 3.3.343.0
  • AWS CLI upgraded from 1.16.6 to 1.16.15
  • Terraform CLI upgraded from 0.11.5 to 0.11.8
  • Terraform AzureRm plugin version 1.16.0
  • Terraform AWS plugin version 1.39.0

Octopus 2018.11

Highlights

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

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

Cloud Dependency Updates

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

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

Database performance updates

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

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

Octopus 2018.12

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

Octopus 2019.1


Highlights

Spaces

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

From our documentation:

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

Teams & Permissions

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


Release Notes

Issues and Bugfixes

  • 5226 - Breaking change Increased the speed of artifact retrieval and cascade deletion when there are many artifacts
  • 5239 - Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server

Upgrading

As with any upgrade for self hosted customers, we recommend taking a database backup first. Given there are some breaking changes to how the built in feed is structured on disk, we also recommend taking a filesystem backup too.

In order to make use of the new Spaces feature, Tentacles should be updated to version 4.0.0, Octopus.Client dependencies should be updated to 5.0.0 and any other integrations should be updated to their latest version.

Breaking Changes

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

Tentacle

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

API Changes

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

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

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

IsMultiTenancyEnabled

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

Built in Repository & Feeds

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

ServerTask links

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

UserRoles

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

Teams

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

ScopedUserRoles

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

Artifacts

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

Permission changes

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

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

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

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

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

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

Accounts

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

Certificates

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

Action Templates

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

Artifacts

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

Audit

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

Cloud Template

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

Deployment

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

Deployment Process

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

Events

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

Feeds

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

Interruptions

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

Library Variable Sets

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

Lifecycles

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

Projects & Project Groups

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

Packages

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

Releases

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

Server Nodes

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

Tasks

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

Tenants

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

Users

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

Octopus 2019.2


Highlights

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

User Invitations into Space Teams

We have added the ability to invite new users into Teams that are owned by Spaces. Previously, new Users could only be invited into System-level Teams, but now Spaces and Space Managers can be self sufficient by inviting new Users without needing to ask a more privileged user to first invite the user into a System team.

Improved Date Display

We've done some renovations around how we handle and display dates. Now, we display dates in your local timezone where possible, and if that isn't possible, we include the timezone, so it's much easier to tell when something happened if you're in a distributed team or in a different timezone to your Octopus Server. Unfortunately, this has meant we've had to make some breaking changes, but we believe the impact will be low.

Breaking Changes

  • The LastSeen property on octopusservernodes/ping now returns an ISO8601 date instead of a formatted string
  • The human-readable Completed date on a Task is now formatted with a timezone
  • The human-readable Published date on a Package is now formatted with a timezone
  • The Rank, LastSeen and IsOffline properties have been removed from the /api/OctopusServerNodes/{id} endpoint, and are now available from a new endpoint /api/OctopusServerNodes/summary
  • The EffectiveExpiryDate on the /api/licenses/licenses-current-status endpoint is now formatted with a Date (yyyy-MM-dd) rather than DateTimeOffset data type.
  • The third party libraries we use to read certificates have been upgraded to newer versions which include tighter certificate verification. This may reject incorrectly formatted certificates.

As this release contains database changes, a database backup is recommended before upgrading. Please ensure you review the steps for upgrading Octopus.

Details

Changes in Octopus 2018.5.6

  • 4576 - Fixes for target ordering in multi-selects and various UX improvements, including minor updates for customers operating at lower resolutions
  • 4600 - Fix project variable helper not including project variables for S3 step
  • 4603 - BugFix - Tentacle upgrade process fails in 2018.5.5
  • 4604 - Fixed bug with custom scripts on Azure RM template step
  • 4509 - Fixed an issue upgrading from versions prior to 3.4 to versions after 2018.4
  • 4548 - Fixed problem where offline drop packages were not using the right escape characters for quoting the variable file as part of the Calamari command
  • 4568 - Fixed bug when updating an existing Service Fabric or Cloud Service target from cmdlets
  • 4572 - Steps now correctly load PowerShell modules when running on the external worker
  • 4587 - Changed behaviour for project with no healthy targets and environment with no dynamic infrastructure
  • 4592 - Corrected values in Azure Environment configuration
  • 4593 - Fixed a bug which prevented Team Edit page from loading
  • 4594 - Perform variable replacement for inline scripts on the Target rather than Server
  • 4596 - Fixed bug where variable usage was not showing on Azure Accounts
  • 4597 - Fixed errors displayed in console relating to missing machine icons
  • 4598 - Fixed error with rendering Azure Account variables

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

  • 4509 - Fixed an issue upgrading from versions prior to 3.4 to versions after 2018.4
  • 4548 - Fixed problem where offline drop packages were not using the right escape characters for quoting the variable file as part of the Calamari command
  • 4568 - Fixed bug when updating an existing Service Fabric or Cloud Service target from cmdlets
  • 4572 - Steps now correctly load PowerShell modules when running on the external worker
  • 4587 - Changed behaviour for project with no healthy targets and environment with no dynamic infrastructure
  • 4592 - Corrected values in Azure Environment configuration
  • 4593 - Fixed a bug which prevented Team Edit page from loading
  • 4594 - Perform variable replacement for inline scripts on the Target rather than Server
  • 4596 - Fixed bug where variable usage was not showing on Azure Accounts
  • 4597 - Fixed errors displayed in console relating to missing machine icons
  • 4598 - Fixed error with rendering Azure Account variables
  • Azure PowerShell Modules - To configure the version of Azure PowerShell modules, we have made a change to the name of the variable. You can now set OctopusUseBundledAzureModules to False.

Changes in Octopus 2018.5.7

  • 4565 - Fixed the managed account hint text on the terraform step
  • 4609 - BugFix - DockerRun command on Windows failing
  • 4612 - Extra options on the setup wizard when requesting a trial key
  • 4613 - Bugfix - Properly encode non-ASCII characters in scripts
  • 4615 - Added ability to attach Terraform logs as artifacts

Changes in Octopus 2018.6.0

  • 4496 - Added RegisterApplicationTypeTimeoutSec to Service Fabric deploy step
  • 4531 - Support for checkbox and drop-down control-types for prompted variables
  • 4571 - Allow migrations by the API between Octopus instances
  • 4605 - External workers have been converted to workers in the default pool and the command line options have been removed, see our documentation on how to manage them
  • 4617 - Fix a bug where confirm dialog is missing when deleting a parent step from the deployment process

Changes in Octopus 2018.6.1

  • 4518 - Improved the rendering performance of the dashboard and project overview when there are a large number of cells to display
  • 4608 - ApiKeys API paging links corrected to stop error in Octopus.Clients and load all keys in the UI when a user has > 30 keys
  • 4610 - Server now checks whether there is enough free space before writing the configuration file
  • 4624 - Fixed a bug that prevented Team Add/Edit page from loading
  • 4626 - The “running tasks” link on the Configuration->Nodes page now filters for running tasks for that node, rather than all tasks on that node
  • 4629 - Added step number to the step edit page

Changes in Octopus 2018.6.2

  • 4383 - Specific and Excluded targets are retained when a deployment fails and it is then re-tried
  • 4415 - Improvements for when choosing a tag with a large number of tenants on the create deployment screen
  • 4590 - Trials started after 30 March 2018 will not fall back to the free Community Edition https://octopus.com/blog/removing-free-tier
  • 4606 - Fix for unknown environment/certificate issue on Service Fabric targets
  • 4627 - Fixing some daily UX frustrations
  • 4631 - The markdown renderer now ignores _ in the middle of words for formatting purposes
  • 4639 - Fixes an issue preventing auto machine cleaning from adding events for machine deletion

Changes in Octopus 2018.6.3

  • 4641 - Set Package Transfer file name with standard name format
  • 4648 - Now correctly excluding disabled deployment targets from licensing limits

Changes in Octopus 2018.6.4

  • 4547 - Project Switcher filter no longer selects the wrong item
  • 4636 - Fix for HashTable parameter error in Service Fabric Deploy Step
  • 4642 - Fixed an error in the accounts overview in Internet Explorer
  • 4651 - Dashboard groups that don't require a scrollbar no longer scroll a few pixel with the mouse wheel
  • 4653 - Improved the speed of Release deletion
  • 4638 - The variable substitution syntax now supports encoding a variable as Base64

Changes in Octopus 2018.6.5

  • 4659 - Fixed error when updating releases on sql servers with case-sensitive collations

Changes in Octopus 2018.6.6

  • 4632 - Special characters in package names are now escaped for offline drops
  • 4656 - Bugfix - Avoid double variable replacement of scripts. Introduced in 2018.5.5
  • 4662 - Dashboard groups are now appropriately resized when filters are applied

Changes in Octopus 2018.6.7

  • 4652 - Output variables created by deployment steps, such as package installation directory, are now passed through to subsequent steps for offline drop targets
  • 4654 - Fixed a bug with channel scoping when evaluating certificate variables
  • 4658 - The dashboard overview is now much quicker if lots of tags are in use
  • 4663 - Fixed an exception loading feeds in Azure steps when lacking the AccountView permission
  • 4670 - Variable evaluation speed has been improved, making (among lots of other things) built-in repository retention much quicker when there are many variables
  • 4674 - Fixed the permissions checks when creating an account ( CVE-2018-12884 )

Changes in Octopus 2018.6.8

  • 2672 - Lifecycle auto-deploy-environment now work with tenants
  • 4533 - Octopus high availability clusters are no longer susceptible to military coup when tasks running on the leader node take too long
  • 4677 - "Script0001 - Release to VariableSet RelatedDocument.sql" can now handle migration of large numbers of library variable sets in releases

Changes in Octopus 2018.6.9

  • 4682 - Reduce polling frequency of project and main dashboards when page is hidden

Changes in Octopus 2018.6.10

  • 4684 - this.replaceLoop is not a function javascript error is now fixed
  • 4683 - Restore ability to substitute additional files when running an inline script
  • 4643 - Fixed issue with trailing spaces on step template names during migrator export

Changes in Octopus 2018.6.11

  • 4538 - Octopus Server node deletion is now vetoed when tasks are still running on the node
  • 4588 - The command Octopus.Server.exe node can now be used to configure Octopus Server nodes
  • 4589 - Creation and deletion of Octopus Server nodes are now audited
  • 4680 - Email step and subscriptions correctly account for team membership via external security groups
  • 4686 - Deployment error variables are now cleared when a new auto-deployment is queued up
  • 4693 - Reinstate variable substitution in TF template files from packages

Changes in Octopus 2018.6.12

  • 4655 - Automatic machine removal no longer logs a warning if a machine doesn't have a machine policy
  • 4657 - Project overview advanced filters now include filter by environment
  • 4666 - Release version filters out spaces now
  • 4678 - Selected packages in a release is now properly populated when migrating a 2.6 instance
  • 4689 - Deployment creation is now faster when there are many previous deployments for that release
  • 4692 - Infrastructure|Environments now uses paging to improve rendering performance on large lists

Changes in Octopus 2018.6.13

  • 4304 - Tasks running on a node that no longer exists are now marked as failed
  • 4466 - Variables to be passed to a Deploy a Release step are only evaluated after being deserialized from JSON
  • 4500 - Output variables are now collected when resuming a child project from an interruption that is deployed using a Deploy a Release step
  • 4553 - Scheduled Trigger for project with Deploy a Release step no longer fails deployment with error The resource 'users-system' was not found.
  • 4646 - Multiple simultaneous interruptions no longer block a deployment from proceeding
  • 4690 - Send email step and test email can now be cancelled
  • 4699 - Server Task Cap and Maintenance Mode state are now included in the output of the show-configuration command
  • 4701 - The UI now caches the available roles, making editing projects quicker when there are a large number of deployment targets

Changes in Octopus 2018.6.14

  • 4696 - Fatal error messages are now displayed on the task summary
  • 4702 - Fixed the "Load more" paging button, broken in 2018.6.12

Changes in Octopus 2018.6.15

  • 4436 - UI improvements to removable list components (for consistency and easy-of-use)
  • 4546 - Cloudformation and Terraform inline script permission required changed to ProcessEdit
  • 4647 - Fixed an issue where legacy variable Octopus.Action.Azure.UseBundledAzurePowerShellModule wasn't being honoured
  • 4669 - Add an option to exclude a machine from the rest of the deployment when using guided failure
  • 4700 - UI improvements to update variable snapshot to make this feature more accessible
  • 4705 - Fixed issue where randomly getting "Cannot read property 'projectIndex' of undefined" error
  • 4706 - Fixed issue where urls referenced in task logs were converted to lowercase during render

Changes in Octopus 2018.7.0

  • 4158 - Octopus now allows multiple external workers, grouped into pools
  • 4561 - Added support for specifying slots on Azure Web App targets and steps
  • 4634 - Fixed query performance for Azure Web Apps
  • 4710 - Fixing an edge-case with Service Fabric targets to deal with self-signed (and password-protected) certificates
  • 4712 - Changed S3 multi file selections bucket key prefix to be optional
  • 4622 - Increased the speed of the Account Usage query

Changes in Octopus 2018.7.1

  • 4739 - Fixed a bug preventing upgrades from Octopus Server 2018.5.7 or earlier directly to 2018.7.0 - please upgrade directly to 2018.7.1 or newer

Changes in Octopus 2018.7.2

  • 4742 - Fixed a bug preventing upgrades to Octopus Server 2018.7.0 or 2018.7.1 with a message like Unrecognised document prefix Accounts- - please upgrade directly to 2018.7.2 or newer
  • 4743 - Fixed a bug which mistakenly deleted non-orphaned library variable set snapshots when upgrading to Octopus Server 2018.7.0 or 2018.7.1 - please upgrade to 2018.7.2 or newer

Changes in Octopus 2018.7.3

  • 4599 - Fixed issue where using Network Service or Local Service account for Windows Service accounts didn't work on non-English systems
  • 4704 - UI indication of default values in project variable templates
  • 4711 - Improved auditing on actions performed by the node command line operation
  • 4715 - Manual intervention completion time is now recorded and logged
  • 4716 - UI fix for environment vs target name filtering on the environments screen
  • 4722 - Fix a bug where leading zero of a certificate's SerialNumber is truncated
  • 4724 - Default to last version during deployment when no valid semver versions exist
  • 4725 - Fixed compatibility issues in our Calamari update script using the -Directory parameter on the Get-ChildItem cmdlet on PowerShell 2.0
  • 4726 - Fixed compatibility issues in Calamari using unsupported security protocols on servers that only have .NET 4.0 installed
  • 4729 - UI adding a delete option to the release overview screen's overflow menu
  • 4730 - Fix a bug where project variables not included in binding dropdowns in Start/Stop App in Tomcat step
  • 4732 - Fix a bug where a null reference exception is thrown when try to save a project in add project dialog before all data are fully loaded
  • 4734 - Fixed Dashboard error "Cannot read property 'projectIndex' of undefined"
  • 4737 - Fix for UI bug in channel design rules
  • 4740 - Fixed script syntax warning message in Azure and AWS PowerShell steps

Changes in Octopus 2018.7.4

  • 4708 - Fixed bug preventing cancelling a deployment that is waiting for manual intervention
  • 4718 - Reduced the amount of data retrieved from the database server for the the project dashboard and process pages, which reduces load on the database server and makes those pages faster when there are many environments
  • 4719 - Fixed a rare issue where equal variable scopes were not be considered equal leading to a variable being added instead of replaced
  • 4727 - UI adding a "HasWarningsOrErrors" flag to the tasks screen filters
  • 4745 - Added an index to the User table
  • 4747 - Fix an issue where OctopusUseBundledAzureModules variable was being ignored

Changes in Octopus 2018.7.5

  • 4513 - Fixed exception when setting up a scheduled trigger for a specific day of the month
  • 4714 - Reduced the CPU usage when deploying to many machine in parallel within the same deployment
  • 4733 - Fixed preservation of JAR manifest info during deployment
  • 4748 - Reduced the amount of data that is retrieved from the database throughout the application
  • 4749 - UI adding an overflow menu option from various documents to the auditing screen
  • 4752 - Fixed Azure Web App deployment failure when no Resource Group is provided
  • 4753 - Run package scripts during Azure Resource Group deployment
  • 4754 - Fixed a bug which limited trial licenses to a single worker and worker pool, when trials are meant to get unlimited workers and worker pools
  • 4755 - Target retention during deployment no longer retrieves all the machines multiple times
  • 4757 - Send additional licensing and usage details back to octopus.com in addition to existing telemetry
  • 4758 - The proxy selection is no longer cleared when expanding the proxy section on the Tentacle details page

Changes in Octopus 2018.7.6

  • 4761 - Halved the performance impact of the project dashboard for instances with many deployments

Changes in Octopus 2018.7.7

  • 4750 - Fixed issue where Deployment Target Triggers didn't trigger for projects with Deploy a release steps
  • 4759 - Removed the extra logging blocks in the deployment log when delta compression is performed
  • 4760 - UI refining both the accounts list and on-boarding panels and reintroducing our green primary buttons (#WooHoo)
  • 4762 - Performance improvements to Project Dashboard query

Changes in Octopus 2018.7.8

  • 4765 - Cloud targets now run health checks via workers
  • 4769 - Fix for dashboard crashes for users who had it configured to show an incompatible set of projects and environments
  • 4770 - Fixed issue with Allow auto user creation being shown as disabled in the portal when it hadn't been explicitly set
  • 4773 - Fixed a performance bug where the SQL Connection Pool could be exhausted by when clients are watching the progress of lots of tasks and the task log storage (usually network storage) is saturated
  • 4777 - UI adding a save option to the 'unsaved changes' dialog
  • 4780 - Fixed an issue that caused cloud target default worker pools to not be used in some situations
  • 4786 - Fixed issue with upgrading the database causing a timeout
  • 4788 - Reworked the dashboard backends to make them quicker and lighten the load on the SQL server

Changes in Octopus 2018.7.9

  • 4795 - Fixed the dashboard query for case-sensitive SQL servers

Changes in Octopus 2018.7.10

  • 4698 - Remove virtual scrolling (and scrollbars) from dashboards and project overviews by default, with an option to turn them on
  • 4797 - Fixed a bug where scopes were sometimes not shown in the variable editor for read only values
  • 4798 - Fixed error when management certificate were being used for Azure Web App targets
  • 4801 - Fixed incorrect account scoping error during health checks when cloud targets were using an account with scope restrictions
  • 4803 - Fix incorrect package upload examples

Changes in Octopus 2018.7.11

  • 4738 - Azure PowerShell Script step now includes Azure CLI
  • 4804 - Added a description of the scripts we plan to run when upgrading the database schema
  • 4807 - UI soften layout transitions with a fade animation
  • 4814 - Subscription number not being picked up when using management certificates

Changes in Octopus 2018.7.12

  • 4580 - Fix for Audit/Event filtering where permissions conflicted or didn't return expected results - CVE-2018-15575
  • 4775 - Allow Azure dropdowns to be refreshed
  • 4806 - Fixed a bug where tenant variable events were not associated with tenant variable documents
  • 4808 - Fixed a bug where removing the sensitive value from a tenant variable would not update the value
  • 4809 - Fixed a bug where the step template side panel showed incorrect data when creating a new step template
  • 4813 - Fixed incorrect usages of Azure APIs that affected Azure private clouds
  • 4819 - Automatic release creation no longer attempts to write to auto deploy logs
  • 4823 - Data subject deletion info and export options as part of user management screens

Changes in Octopus 2018.7.13

  • 4751 - Service Fabric Script steps now use the new Service Fabric targets
  • 4768 - UI make re-deploy actions more discoverable and deploy actions less scary
  • 4799 - Fixed an issue where a large number of queued tasks would increase the time to start each of those tasks
  • 4816 - Lifecycle phase Required to Progress now respects value entered for Minimum # must complete option
  • 4818 - Added a warning when the first Worker is added to the default pool
  • 4825 - Resolved an issue that caused tasks and background processes to hang and also not cancel
  • 4829 - Reduced the number of times all machines are retrieved from the database

Changes in Octopus 2018.7.14

  • 4720 - Fixed an issue when cloning a project with scheduled triggers scoped to channel
  • 4766 - Fixed an issue where we were trying to deploy a child project after resuming from a manual intervention when that child project shouldn't be deployed due to deployment condition selected
  • 4771 - UI Optimise wasted space on the dashboards
  • 4790 - Octopus Server logs are now manually flushed when shutting down to avoid losing any messages written just prior to shut down
  • 4835 - Added DeploymentProcess link to deployment api response
  • 4837 - Improved descriptiveness of the scheduled task cleaner when it cleans up old task logs

Changes in Octopus 2018.8.0

  • 4560 - Allow CloudFormation steps to specify RoleARN for the stack
  • 4695 - Add CloudFormation change set feature and add apply change set step
  • 4736 - UI to show cloned project information
  • 4793 - Fix an issue where s3 multiple file selections would not retain folder structures
  • 4800 - Fixed script syntax warning when no script syntax provided
  • 4828 - Fixed issue with logging in to non-default Azure Clouds with Azure CLI
  • 4842 - Reference Packages from Script Steps
  • 4843 - Variable Substitution Features from Script Steps
  • 4848 - Initial Kubernetes Support

Changes in Octopus 2018.8.1

  • 4850 - Fixed a bug where environments filter wasn't shown on the tasks page for users with scoped EnvironmentView permission
  • 4851 - Updated AWS CLI to version 1.16.6
  • 4852 - Fix an issue where a legacy azure web app would show an error when account or web site is bound
  • 4853 - Token account type is now visible in the UI

Changes in Octopus 2018.8.2

  • 4746 - Provide a bigger dialog when editing in-line ARM, CF and Terraform templates
  • 4838 - The data migration API /api/migrations/import now runs under the correct security context
  • 4847 - Markdown links are now shown correctly in highlight and fatal messages on the the Task Summary tab
  • 4856 - Fix for Azure Resource Group (ARM) step bug
  • 4858 - Packages from AWS ECR feeds will now show option to 'Not Acquire'
  • 4862 - UI adding concept images to help visualise the execution location/strategy in steps
  • 4863 - Server Web Request Proxy configuration now shown in Configuration - Settings
  • 4744 - Fixed null reference when viewing community step templates
  • 4767 - Check if worker pools are available to prevent null reference in summary UI

Changes in Octopus 2018.8.3

  • 4266 - Fixed Halibut issue where connections were kept open by the server
  • 4812 - Improved messaging for different failure scenarios when running the database schema upgrades to be clearer about the state of their database, what they can do to get back up and running, and how to get help if they need it
  • 4824 - Fixed memory issue in Halibut
  • 4833 - Octo.exe, Octopus.Client and the TeamCity plugin (version 4.41.0+) now use delta compression when pushing packages to the Octopus Server
  • 4866 - Kubernetes container name validation now accepts variables
  • 4867 - Helm Kubernetes Release Name now shows the variable bindings
  • 4868 - Kubernetes service port names now accept variables
  • 4870 - Fixed an error on the project dashboard if project ids on releases are lowercase

Changes in Octopus 2018.8.4

  • 4855 - Support for proxies in Azure CLI commands in Azure PowerShell script steps
  • 4859 - Variable substitution syntax now support replacement of text using regular expressions
  • 4860 - Support for proxies in AWS CLI in AWS CLI script steps
  • 4861 - Fixed a UI exception when deleting a user
  • 4865 - Added validation to ensure the project is entered on the Deploy Release step
  • 4876 - Added validation to the Windows Service step
  • 4879 - Azure CLI configuration written to subdirectory of Calamari working directory to avoid clashes with Variable Substitution
  • 4880 - Navigation shortcut via overflow menu from User Profile and User Listing pages to the Test Permissions page
  • 4881 - Create a user invite link directly from the Team edit page
  • 4882 - Improved handling of variable merging when using Octopus.Migrator.exe to import to a server where the project already exists
  • 4886 - The Octopus.Upgrader.exe file is now digitally signed allowing automatic Tentacle upgrades to work in environments where untrusted/unsigned executables are prevented from running
  • 4889 - Resolved issue with packages not being acquired when role matched no targets

Changes in Octopus 2018.8.5

  • 4266 - Fixed Halibut issue where connections were kept open by the server
  • 4824 - Fixed memory issue in Halibut
  • 4844 - Fix for Azure Web App query not returning resource groups
  • 4872 - Fixed a error on the tenants screen after updating the name of a tag
  • 4888 - Fixed a bug where triggers could create releases with invalid versions
  • 4893 - Helm step now visible when Kubernetes steps are enabled
  • 4895 - Fixed an issue where a package is reported as not acquired on a Worker even though it was
  • 4896 - Variable-substitution and config-transform features enabled for Azure PowerShell script steps and Azure Service Fabric script steps

Changes in Octopus 2018.8.6

  • 4467 - UI improving the messaging/intuitiveness around the “Include all Tenants” checkbox on the deployment screen
  • 4877 - Remove trailing white space from folder paths when using Octopus.Migrator.exe export
  • 4892 - Fix to orphaned project reference for cloned projects
  • 4899 - Provide the ECR registry URL as a variable when using an image from the ECR or Docker feed type
  • 4901 - Fixed a bug with "Deploy a release" steps not being available for selection in channel version rules
  • 4904 - UI improvements to client-side rendering for tenants screen and project overviews
  • 4906 - Resolved issue with Tomcat and WildFly steps not being performed during deployments
  • 4907 - Azure web app with scoped AccountView permission can now modify the Azure account

Changes in Octopus 2018.8.7

  • 4616 - Log additional detail for failure messages on ARM deployments
  • 4764 - Encrypt and write output variables to a file instead of passing them as a base64 encoded string for offline drop targets
  • 4894 - Resolved issue with absolute paths to staged packages in offline-drops
  • 4905 - Enable the ECR feed type for use in the kubernetes steps
  • 4909 - Fix a bug where WorkerPool and Environment is not populated when adding Worker and Deployment Target
  • 4912 - Newly added environments now appear on the dashboard correctly
  • 4913 - Resolved issue with terraform steps not working through a proxy
  • 4914 - Kubernetes Ingress host now accepts plain subdomains (e.g. http://example.org|example.org)
  • 4916 - Reword 'Helm Update' command as 'Helm Upgrade'
  • 4919 - Fixed an bug that stopped deployments from completing when an error occurred writing to the system log
  • 4921 - Fixed "forcibly closed" error occurring in tentacle communications
  • 4922 - Resolved issue migrating releases which contain named package references
  • 4933 - Resolved issue where packages were not being displayed in release for Deploy a Release steps

Changes in Octopus 2018.8.8

  • 4785 - Added ability to run script console on workers or worker pools
  • 4917 - Fix to show some missing usage reporting of Azure accounts in release snapshots
  • 4923 - Fix an issue where editing a lifecycle does not show correctly if the phase does not override the default retention policy
  • 4926 - Fix an issue where default worker pool wasn't selected by default for some steps when first created
  • 4936 - Kubernetes liveness probe scheme selection fixed
  • 4937 - Added additional validation for the Kubernetes target cluster URL
  • 4938 - Resolved issue with channel version rules for script step package references being lost when modifying deployment process
  • 4939 - Fix for incorrect warnings from migrator about missing machines

Changes in Octopus 2018.8.9

  • 4404 - Fixed issue with running scriptcs on mono version 5.10 or newer
  • 4620 - Fixed exception when using Tentacle show-configuration command when no certificate is configured
  • 4703 - Made the license command more resilient and added a command-line switch to --skipLicenseCheck
  • 4875 - Improved how the license command handles encodings with the --licenseBase64 parameter
  • 4900 - Fixed proxy environment variables for authenticated proxies
  • 4903 - Fix a bug where project cannot be cloned when it has a scheduled trigger
  • 4918 - Fixed issue with application assembly references clashing with Azure PS references
  • 4924 - UI fix for Library Certificates paging issue
  • 4927 - Added add\refresh button to feed selection
  • 4931 - Ensure Helm values supplied by the Key/Value option are properly exploded
  • 4932 - Variable Sets used by a large number of snapshots no longer produce an error when deletion is attempted
  • 4934 - Exposed pod and container security context options for Kubernetes steps
  • 4935 - Tenant tags and tag sets are now correctly displayed in the order defined in the tag set
  • 4943 - Okta authentication provider updated so SSO now triggers login in Octopus portal
  • 4945 - The --instance command line argument is now case insensitive and required in fewer circumstances
  • 4946 - Multi-select drop downs (as used on the Manage Tenant Tags dialog) no longer open by default
  • 4950 - Fix a bug where project setting and create deployment page should not require TenantView permission for untenanted project
  • 4951 - Fixed a bug where onboarding would make duplicate requests after navigating around the UI
  • 4952 - Kubernetes authentication options are now more clearly defined
  • 4955 - Added better error message when kubectl could not be found
  • 4960 - Fixed backwards compatibility in Octopus.Client ProjectEditor.CreateOrModify function
  • 4961 - Azure and AWS logins supported for K8S targets
  • 4962 - The license command now allows licence as an alias
  • 4963 - The license command can now accept the license via a file
  • 4965 - SSH health checks no longer block other scripts from running on the same target
  • 4972 - Added filters to the api/reporting/deployments/xml endpoint
  • 4974 - Fixed an edge case where the ETag would not update
  • 4977 - The Configuration->Nodes page can now be filtered if there are multiple nodes
  • 4978 - New-OctopusKubernetesTarget can now be used to create new K8S targets
  • 4980 - Remove support for Ssl3.0
  • 4981 - Allowed Recreate and Rolling Update strategies to wait for the K8S deployment to finish

Changes in Octopus 2018.8.10

  • 4982 - Search field on “Include a Script Module” is now case-insensitive
  • 4983 - K8S Secret and ConfigMap resources no longer deployed when the feature is disabled
  • 4984 - K8S suggestion lists are now case insensitive
  • 4985 - K8S Ingress host allowed variable substitution
  • 4986 - Exposed annotations on the K8S deployment resource
  • 4987 - Added extra help to the OpenID Connect authentication providers
  • 4988 - BugFix: Acquisition of Helm charts fails when the username is empty
  • 4992 - Fix for migrator importing proxies

Changes in Octopus 2018.8.11

  • 4949 - Allow additional Kubernetes resources to participate in the Deploy Containers lifecycle
  • 4994 - Validation rules now prevent creating an Ingress without a Service in the Deploy Kubernetes containers step
  • 4996 - Fixed a race condition in the UI during onboarding
  • 5001 - Fix for tenant variable loading issues with > 2100 tenants

Changes in Octopus 2018.8.12

  • 4958 - Fixed an issue with NuGet feeds when migrating from 2.6 to versions later than 2018.8.0
  • 4973 - Machines that trigger an auto deploy event while a tenanted deployment is in progress will now receive that deployment when it finishes
  • 4975 - Fixed a rare crash that occurred when attempting to write log files
  • 4991 - Add backwards support to deploy Service Fabric applications using CloudRegion targets
  • 4998 - Terraform Apply step now supports multi-line output variables
  • 4999 - Added a null check for a missing ActionName in GetPackageVersionsUsedInReleases
  • 5005 - Bugfix: Kubernetes volume mount validation when using raw YAML

Changes in Octopus 2018.9.0

  • 4302 - The built-in worker command-line interface handles machine\user and domain\user formats more gracefully
  • 4574 - Updated the Azure PS bundle to 6.8.1 and the Azure CLI to 2.0.45
  • 4774 - Offline-Drop targets can now store the bundle as an Octopus Artifact
  • 4871 - The interruption and artifact APIs now have an ETag, lessening the load on the database
  • 4953 - In 2018.8 it was possible to corrupt auto-release-creation and channel rules by renaming package references on script steps
  • 4954 - Allow script step package references to be used for project versioning
  • 4970 - Updated the AWS PS bundle to 3.3.343.0 and the AWS CLI to 1.16.15
  • 4971 - Updated Terraform to 0.11.8, the AzureRM plugin to 1.16.0, and the AWS plugin to 1.39.0
  • 4989 - Fix for error reporting missing variable set snapshot NullReferenceException during deployments and variable set editing
  • 4990 - Built-In Worker settings are now displayed on the Configuration->Nodes->Server Settings page
  • 4995 - Exposed annotations for the pod resources created by the Kubernetes deployment resource
  • 4997 - The path command-line interface now validates paths and tries to create the path if it does not exist
  • 5017 - The Octopus.Server.exe database --upgrade --skipLicenseCheck command actually skips the license check properly now
  • 5018 - Fixed a bug with auto login when only the Active Directory provider was enabled
  • 5019 - K8S service annotations now exposed like Ingress and Deployment annotations

Changes in Octopus 2018.9.1

  • 5023 - User accounts from certain email domains can be excluded from billing at the discretion of the service provider
  • 5025 - Improvements to concurrency protection on variable sets
  • 5026 - Call to api/projects?name=[test] fails because of the special chars
  • 5027 - Sensitive Template Project variables on a Tenant will now show "value required" warning when they are empty
  • 5028 - Now preventing the SQL Database connection string from containing both Integrated Security and SQL Authentication with User ID or Password to prevent confusion
  • 5035 - Bundled Tentacle 3.23.2 which fixes a bug in the Tentacle Manager that was preventing showing instances
  • 5036 - 2018.9.0 introduced an issue where upgrading was converting offline-package-drop targets to use artifact mode
  • 5042 - 2018.8.0 introduced an RCE flaw in YAML parsing (CVE-2018-18850) which is now rectified

Changes in Octopus 2018.9.2

  • 5029 - UI improve the lifecycles list for long lifecycles
  • 5039 - Updated the UI design and user-experience when adding new deployment targets/workers
  • 5041 - The task summary page now shows the channel chip
  • 5044 - Resolved issue with multiple channel rules introduced in 2018.9.0
  • 5046 - Instead of limiting workers and worker pools by licensing, we now only limit workers themselves, allowing you to create as many worker pools as you want
  • 5047 - Sensitive output variables are now masked in the task logs of child steps (CVE-2018-18900)

Changes in Octopus 2018.9.3

  • 4969 - Dashboard can be cached longer than 2 seconds
  • 5037 - Step template usages are now sorted alphabetically
  • 5043 - Show more informative summary text for an Active Directory identity when the specified account has no email address set
  • 5048 - Added pod and node affinity settings to the k8s container deployment step
  • 5050 - Only show the channel chip on the task summary page if the project has more than one channel
  • 5051 - Migrator now remaps Deploy Release step projects

Changes in Octopus 2018.9.4

  • 4849 - Deployments are now removed from the dashboard again when they or their release is deleted
  • 4957 - The dashboard now correctly shows the updated version number of a release again when it is changed
  • 5054 - Resolved issue introduced in 2018.9.0 where updating step template usages was causing exception when viewing project

Changes in Octopus 2018.9.5

  • 5024 - Database upgrade scripts now consistently roll back to the last known good state regardless of which specific kind of upgrade script fails
  • 5038 - Database upgrade scripts now use an infinite SQL command timeout consistently - we really want the upgrade to complete even if a particular command takes a longer time than expected
  • 5055 - K8S standalone Secret and ConfigMap steps deploy as expected now

Changes in Octopus 2018.9.6

  • 5013 - Significant decrease in the amount of data persisted with deployments, especially when using a large number of certificates
  • 5059 - Increased the database connection timeout and transaction commit/rollback timeout for database upgrades to 3 minutes, just like it was before 2018.9.0
  • 5063 - Fixed validation for kubernetes volumes that referenced external configmaps or secrets

Changes in Octopus 2018.9.7

  • 5020 - fixed some rare cases of certificate read failures after upgrading to 2018.8.7
  • 5032 - Fix a bug where IE 11 does not render artifacts URL correctly
  • 5056 - UI legacy toggle on Azure steps to access older template functionality
  • 5058 - Fixed issue with Deploy Release step not always failing when the release fails
  • 5061 - Enable full screen mode for the variable editor dialog
  • 5065 - migrator.exe now correctly handles the default worker pool selected by certain deployment targets, where the selection would have been dropped during the import process
  • 5068 - Folders with Junctions can now be deleted again
  • 5069 - migrator.exe now correctly handles the worker pool selected for actions in a deployment process, where the selection would have been dropped during the import process
  • 5070 - kubectl config file is now displayed in the verbose logs
  • 5071 - The package cache and working directory can now be configured
  • 5076 - Fixed up integration with http://Quay.io|Quay.io docker repo

Changes in Octopus 2018.9.8

  • 4920 - Fixed issue with packages not being listed when using TeamCity 2018.1.x legacy NuGet feeds
  • 5066 - Fixed an issue with the S3 step where invalid bucket keys were being used when using multiple file selections
  • 5072 - migrator.exe now gracefully handles the importing tenant + project + environment connections when the project or environment does not exist in the target
  • 5081 - migrator.exe now correctly handles importing subscriptions which are filtered by tenant tags

Changes in Octopus 2018.9.9

  • 5021 - Kubernetes target certificates now reported in certificate usage
  • 5052 - User accounts for Octopus Support Staff can now be added to an Octopus Server regardless of license limits
  • 5054 - Resolved issue introduced in 2018.9.0 where updating step template usages was causing exception when viewing project
  • 5079 - Resolved logging format exception when executing database upgrade script
  • 5080 - Fix a bug where wrong permission is used when try changing lifecycle for a project
  • 5087 - migrator.exe now correctly handles importing variable values scoped to tenants via tenant tags

Changes in Octopus 2018.9.10

  • 4817 - Subscription emails now display events in ascending order by the time the event occurred
  • 4846 - Reduced queue time in some instances for tasks resuming from manual intervention
  • 4941 - Guided failure for required steps no longer presents the option to skip the step or exclude a machine from the step
  • 5077 - Exposed image pull policy settings for K8S containers
  • 5078 - Standalone ingress rules now accept variable host names
  • 5080 - Fix a bug where wrong permission is used when try changing lifecycle for a project
  • 5082 - migrator.exe now correctly handles importing accounts restricted to environments or tenants where some of those environments or tenants do not exist in the target
  • 5084 - migrator.exe now correctly handles importing project triggers which filter events for certain environments where some of those environments do not exist in the target
  • 5085 - migrator.exe now correctly handles importing deployment targets belonging to certain environments or tenants where some of those environments or tenants do not exist in the target
  • 5086 - migrator.exe now correctly handles importing account variables, where before the account variable was not remapped correctly from source to target
  • 5090 - Fixed issue with subscription webhooks using wrong http header type
  • 5093 - Octopus Cloud licenses are excluded from compliance pre-condition checks when upgrading the database or applying a new license
  • 5094 - If a database upgrade script is running for a long time without showing any progress messages, we now log a "still working" message every minute until the script completes

Changes in Octopus 2018.9.11

  • 5095 - Resolved issue where project versioning-strategy was being cleared when upgrading from Octopus 2018.8.x to 2018.9
  • 5097 - Fix a bug where VariableSet cannot be retrieved through Deployment.ManifestVariableSetId when there is variable scoped to channel
  • 5098 - Fix for Service Fabric targets API failing to retrieve store location/name override
  • 5100 - migrator.exe now correctly exports library variable sets used by a project and any of its releases, where beforehand any library variable sets removed from the project would not be exported subsequently causing the import to fail
  • 5101 - Migrator now correctly remaps tenant tag references when the tag-set exists on the destination

Changes in Octopus 2018.9.12

  • 4411 - Fix text color of Tenant Tag tooltip so description is visible
  • 4672 - Fix an issue where enter causes the variable editor to save when adding a new variable
  • 4947 - Fix an issue where bottom action buttons for lists would be duplicated or constantly appear and disappear
  • 5060 - Changing a projects lifecycle now correctly re-renders the phases and environments
  • 5091 - Fix F# compatibility with mono version 5.16
  • 5103 - Improved summary text for subscription filters
  • 5104 - Added Octopus.Machine.Hostname to automatic variable completion list
  • 5105 - Added help text for User Profile -> Api Keys
  • 5106 - Ensure deployment target icons are shown at smaller screen resolutions
  • 5107 - The icon on disabled chips is now grayed out in the same way as the text
  • 5108 - Infrastructure page now correctly shows worker pools and workers tabs when user has permission
  • 5109 - Fixed missing variable icon overlapping the project name on the tenant variable screen
  • 5111 - Long project names no longer overlap the selected environments on the tenant variable screen
  • 5112 - Fix an issue where default ports were not provided for ssh and listening tentacles during creation
  • 5113 - Helm deployments fail with target using cloud account
  • 5114 - API key creation now creates an audit log, regardless of who you create the key for
  • 5120 - New NGINX feature available when deploying a package to SSH Deployment targets

Changes in Octopus 2018.9.13

  • 4156 - Fixed highlighting of the selected element in drop downs that allowed filtering (e.g. the Add Member to Team dialog)
  • 5116 - Fixed validation around Java package steps that could be saved without selecting a package
  • 5117 - migrator.exe now correctly exports all dependencies used by a project and any of its releases, where beforehand any dependencies removed from the project would not be exported subsequently causing the import to fail
  • 5119 - migrator.exe now correctly exports all versions of any action templates used by a project and any of its releases, where beforehand only the specific versions in use were exported causing potential errors after import
  • 5122 - Tweaked shortcut menu for package feeds to make common actions more discoverable
  • 5125 - Long project names will now wrap in the project quick search dropdown
  • 5127 - migrator.exe partial-export now supports exporting multiple projects by specifying the --project="MyProjectName argument multiple times, or by project groups using the new --projectGroup="MyProjectGroup1" argument or in any combination of the two
  • 5132 - The count of releases and deployments sent to octopus.com as telemetry has been corrected to use the DeploymentHistory table

Changes in Octopus 2018.9.14

  • 5137 - We fixed how the database collation is calculated while upgrading Octopus Server, which was previously reported to fail under certain circumstances using Azure SQL Database

Changes in Octopus 2018.9.15

  • 5135 - Resolved script step package references being incorrectly deleted by retention policy
  • 5136 - Create release page shows project ID rather than name for Deploy Release steps
  • 5139 - Extend brute force login protection to cover API keys

Changes in Octopus 2018.9.16

  • 5143 - Added the Strict-Transport-Security HTTP header to the page shown when Octopus Tentacle is accessed from a Web Browser
  • 5148 - migrator.exe import will no longer fail with a unique constraint violation on name when it mistakenly tried to insert a new MachinePolicy or Subscription or Account or Feed with the same name, now it will correctly overwrite the existing document
  • 5149 - Clicking on a step in the task summary now navigates you to the correct element in the task log
  • 5152 - Added a new update-trust command for Tentacle, this command allows you to update a server thumbprint, without having to remove and then add a new thumbprint which doesn't work for polling Tentacles
  • 5153 - Fixed a regression in Octopus.Migrator.exe partial-export introduced in 2018.9.13 which would incorrectly fail to validate the arguments related to exporting releases
  • 5155 - Support for Kubernetes Container Lifecycle Events

Changes in Octopus 2018.9.17

  • 5133 - UI Simplifying the Getting Started / Onboarding guides
  • 5144 - Resolved issue with migrator partial-export command exceeding 2100 SQL parameters
  • 5145 - Added the ability to choose how inlined scripts in deployment processes are exported by Octopus.Migrator.exe including CopyInlineScripts (current behaviour), ExtractInlineScripts, and LeaveInline - learn more
  • 5147 - Fixed issue where editing an offline drop removes the encryption password
  • 5154 - Updated task logs for subscription processing and auto-deploy to use nesting and add links to the related project / trigger / release
  • 5163 - Fix error on project process screen when user does not have LifecyleView permissions
  • 5164 - Show empty state info boxes when connecting a tenant to a project or tag set and none exist
  • 5165 - Made the Azure account type expander look and work in the same way as other expanders
  • 5166 - Improved layout of Upload Package dialog
  • 5170 - OctopusClient updated to include information in it's calls that allow filtering in the audit log
  • 5171 - Octopus Cloud instances can now be licensed by deployment target just like self-hosted Octopus Server licenses
  • 5167 - Gracefully stop Octopus Server if running in terminal and process terminated

Changes in Octopus 2018.10.0 LTS

  • 5126 - Fix for error saying unable to delete a step template that's in use

Changes in Octopus 2018.10.1 LTS

  • 5235 - Fragmented database indexes are automatically rebuilt or reorganized after other upgrade script have run
  • 5236 - UI fix for variable editor popover menus being visually cut off

Changes in Octopus 2018.10.2 LTS

  • 5246 - New-OctopusAzureWebAppTarget command slot name parameter is now honoured

Changes in Octopus 2018.10.3 LTS

  • 5287 - Prevented infinite polling loop when navigation happens while request is in flight

Changes in Octopus 2018.10.4 LTS

  • 5314 - Save terraform sensitive values as Octopus sensitive values (CVE-2019-8944)

Changes in Octopus 2018.10.5 LTS

  • 5336 - Database upgrade script failed with a InvalidOperationException

Changes in Octopus 2018.10.6 LTS

  • [5438/droyad] - Improved the performance the Projects API when many projects use features that are based on step names
  • [5439/droyad] - Improved the speed of the automatic release creation after a package upload
  • [5456/droyad] - Improved the performance of the permission loading that occurs after a Team, User or Role is changed

Changes in Octopus 2018.10.7 LTS

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

Changes in Octopus 2018.11.0

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

Changes in Octopus 2018.11.1

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

Changes in Octopus 2018.11.2

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

Changes in Octopus 2018.11.3

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

Changes in Octopus 2018.12.0

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

Changes in Octopus 2018.12.1

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

Changes in Octopus 2019.1.0

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

Changes in Octopus 2019.1.1

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

Changes in Octopus 2019.1.2

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

Changes in Octopus 2019.1.3

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

Changes in Octopus 2019.1.4

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

Changes in Octopus 2019.1.5

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

Changes in Octopus 2019.1.6

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

Changes in Octopus 2019.1.9

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

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

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

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

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

Changes in Octopus 2019.1.10

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

Changes in Octopus 2019.1.11

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

Changes in Octopus 2019.2.1

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

Changes in Octopus 2019.2.2

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

Changes in Octopus 2019.2.3

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

Changes in Octopus 2019.2.4

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

Changes in Octopus 2019.2.6

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

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

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

Changes in Octopus 2019.2.7

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

Changes in Octopus 2019.2.8

  • 3748 - Fix for editing a release with a package that doesn't match channel rules
  • 5272 - Octopus Cloud Octopus Manager team doesn't have permissions to export users permission structure
  • 5404 - Fix for broken Project settings page if project was cloned from another project that's not available due to permission/deletion/migration
  • 5422 - Made the getting started guidance available to hosted customers and space managers
  • 5423 - Adding null checking around database upgrade script
  • 5425 - Docker acquisition script moved from Server to Calamari

Changes in Octopus 2019.3.0 LTS

2019.3 LTS