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 4.1.9 to 2019.11.1

Octopus 2019.11

Highlights

Official Jenkins Plugin and Operations Runbooks

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

Breaking changes

Octopus API and Octopus.Client

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

Octopus 2019.10

Highlights

Flexible Linux deployments, PowerShell Core support, Operations RunBooks EAP

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

Read our blog post to learn more.

Breaking changes

PowerShell Core

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

Build Information

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

Octopus 2019.9

Highlights

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

Read our blog post to learn more.

Breaking changes

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

Octopus 2019.8

Highlights

2019.8 includes:

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

See our blog post for the full details.

Breaking changes

No breaking changes in this release.

Octopus 2019.7

Highlights

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

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

Breaking changes

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

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

Octopus 2019.6

Highlights

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

Read our [Octopus 2019.6 blog post to learn more.

Breaking changes

This release includes the following breaking changes:

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

Octopus 2019.5

Highlights

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

Read our blog post to learn more.

Breaking Changes

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

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

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

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

Octopus 2019.4

Highlights

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

Read our blog post to learn more.

Breaking Changes

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

Octopus 2019.3

Highlights

Octopus Server 2019.3 LTS is a roll-up release of Octopus 2019.1 and Octopus 2019.2 and the headline feature is Spaces which enables teams to group projects, environments, tenants, step templates, and other resources into a Space. It also includes a large number of enhancements and bug fixes along with database performance and cloud dependency updates.

Read our blog post to learn more.

Breaking changes

This release includes numerous break changes from the introduction of Spaces. Refer to the Octopus Deploy 2019.1 release highlights for the full details.

Octopus 2019.2

Highlights

User Invitations into Space Teams

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

Improved Date Display

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

Breaking Changes

  • The LastSeen property on octopusservernodes/ping now returns an ISO8601 date instead of a formatted string
  • The human-readable Completed date on a Task is now formatted with a timezone
  • The human-readable Published date on a Package is now formatted with a timezone
  • The Rank, LastSeen and IsOffline properties have been removed from the /api/OctopusServerNodes/{id} endpoint, and are now available from a new endpoint /api/OctopusServerNodes/summary
  • The EffectiveExpiryDate on the /api/licenses/licenses-current-status endpoint is now formatted with a Date (yyyy-MM-dd) rather than DateTimeOffset data type.
  • The third party libraries we use to read certificates have been upgraded to newer versions which include tighter certificate verification. This may reject incorrectly formatted certificates.
  • The write-verbose PowerShell Cmdlet now mimics native PowerShell behavior more closely - write-verbose "myvar = " $myvar is no longer valid and will throw a positional parameter cannot be found error. Please use write-verbose "myvar = $myvar" instead.

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

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

Changes in 2018.3

See our release blog post for more details.

New Features

This month, we've greatly improved our support for infrastructure as code unlocking some incredible deployment automation and infrastructure automation scenarios. Octopus 2018.3 introduces support for GitHub repositories as feeds and first class terraform support as well as some awesome smaller features like Highlight Messages and Artifacts and . Read on for all the exciting details!

Upgrading

This release contains a few post-install data fixes that may take some time (depending on the size of your DeploymentProcess and Events tables), so please ensure you allow time for this to complete. If you are running the watchdog service, please ensure this is stopped during the upgrade.

All of the usual steps for upgrading Octopus Deploy apply.

Octopus 2018.2

Changes in 2018.2

See our release blog post for more details.

New Features

Octopus 2018.2 brings a number of exciting new features including the much requested step to deploy a release, the ability to deploy AWS CloudFormation templates, delete existing CloudFormation stacks, and run scripts with the AWS CLI.

Breaking Changes

If you are using an older version of Octopus.Client.dll to access /api/feeds/all then this will now error. You will need to update to >= 4.30.7 of Octopus.Client. The reason for this is that we have added a new feed type for releases of Octopus projects, to support the new Deploy Release step.

In anticipation of some upcoming new feed types we have hit the point where we were forced to revisit how we expose the packages API for external feeds, and how we store cached packages for deployments. Unless you are hitting the Octopus API directly to search through your external feeds or rely on specific naming of the cached packages, then there should be almost no impact to you. One side effect of the change to package cache names is that the current packages cache on the server and tentacles will be no longer checked so new deloyments will use the new package names. More details about these changes are available in the GitHub tickets "Packages API does not meet the requirements of our expanding feed types #4114" and "Modify the cache naming format to allow for new feed formats #4211".

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

Octopus 2018.1

Changes in 2018.1

See our release blog post for more details.

New Features

This January release of Octopus Deploy is primarily a security release driven by Octopus Cloud and will also benefit each of our customers running Octopus Deploy on-premises. We highly recommend upgrading.

You'll also notice our new versioning strategy: what would normally have been Octopus 4.2 is actually 2018.1. Read more about why we changed.

Improvements

  • When installing Octopus Server and using a Custom Windows Account to run the service, the installation wizard will configure SQL Server correctly so the Custom Windows Account can access the database
  • Steps may now be explicitly configured to run before or after package acquisition
  • The built-in worker, which executes deployment steps and scripts on the Octopus Server, can now be configured to run using a different, lower-privileged user account
  • Fix for infrastructure overview not correctly flowing tag sets from associated tenants
  • Import using the Octopus migrator finds the correct deployment process for scripts from similarly named projects
  • Existing orphaned channels and releases are removed from the database
  • The check to see whether a step template is in use is now much quicker
  • Environments, channels and tags now cannot be deleted if they are used by a disabled step in a project's current process
  • Package notes are fetched in bulk and in async, meaning a release can be deployed without all notes being downloaded first
  • The installed version of Octopus Server is now tracked to help us provide support when data issues occur and is a precursor to raising and event on upgrade

Breaking Changes

Auto machine removal now happens as part of health checks. Minor breaking change API endpoint for machine removal logs is removed and machine removal logs are no longer stored on the Octopus server

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

Octopus 4.1

Changes in 4.1

See our release blog post for more details.

New Features

This December release of Octopus continues the support for Java that was introduced back in 3.17, with the ability to export certificates as Java KeyStores, as well as configuring certificates directly within existing Tomcat 7+, WildFly 10+ and Red Hat JBoss EAP 6+ application servers. This release also allows Maven repositories to be configured as external Octopus feeds, meaning Octopus can now consume Maven artifacts as part of a deployment.

Improvements

  • Maven repositories as external feeds
  • Deployment of Java keystores and configuration of certificates in WildFly, JBoss EAP and Tomcat
  • Directories for task logs, artifacts and the package repository are now store as relative paths

Breaking Changes

There are no breaking changes in this release.

Upgrading

All of the usual steps for upgrading Octopus Deploy apply.

Release notes

These are the features and fixes you'll get by upgrading from 4.1.9 to 2019.11.1.

Changes in Octopus Server 2019.11.1

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

Changes in Octopus Server 2019.11.0

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

Changes in Octopus Server 2019.10.12

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

Changes in Octopus Server 2019.10.11

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

Changes in Octopus Server 2019.10.10

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

Changes in Octopus Server 2019.10.9

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

Changes in Octopus Server 2019.10.8

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

Changes in Octopus Server 2019.10.7

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

Changes in Octopus Server 2019.10.6

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

Changes in Octopus Server 2019.10.5

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

Changes in Octopus Server 2019.10.4

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

Changes in Octopus Server 2019.10.3

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

Changes in Octopus Server 2019.10.2

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

Changes in Octopus Server 2019.10.1

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

Changes in Octopus Server 2019.10.0

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

Changes in Octopus Server 2019.9.8

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

Changes in Octopus Server 2019.9.7

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

Changes in Octopus Server 2019.9.6

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

Changes in Octopus Server 2019.9.5

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

Changes in Octopus Server 2019.9.4

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

Changes in Octopus Server 2019.9.3

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

Changes in Octopus Server 2019.9.2

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

Changes in Octopus Server 2019.9.1

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

Changes in Octopus Server 2019.9.0

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

Changes in Octopus Server 2019.8.6

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

Changes in Octopus Server 2019.8.5

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

Changes in Octopus Server 2019.8.4

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

Changes in Octopus Server 2019.8.3

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

Changes in Octopus Server 2019.8.2

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

Changes in Octopus Server 2019.8.1

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

Changes in Octopus Server 2019.8.0

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

Changes in Octopus Server 2019.7.13

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

Changes in Octopus Server 2019.7.12

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

Changes in Octopus Server 2019.7.11

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

Changes in Octopus Server 2019.7.10

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

Changes in Octopus Server 2019.7.9

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

Changes in Octopus Server 2019.7.8

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

Changes in Octopus Server 2019.7.7

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

Changes in Octopus Server 2019.7.6

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

Changes in Octopus Server 2019.7.5

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

Changes in Octopus Server 2019.7.3

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

Changes in Octopus Server 2019.7.2

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

Changes in Octopus Server 2019.7.1

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

Changes in Octopus Server 2019.7.0

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

Changes in Octopus Server 2019.6.13

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

Changes in Octopus Server 2019.6.12

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

Changes in Octopus Server 2019.6.11

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

Changes in Octopus Server 2019.6.10

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

Changes in Octopus Server 2019.6.9

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

Changes in Octopus Server 2019.6.8

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

Changes in Octopus Server 2019.6.7

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

Changes in Octopus Server 2019.6.6

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

Changes in Octopus Server 2019.6.5

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

Changes in Octopus Server 2019.6.4

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

Changes in Octopus Server 2019.6.3

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

Changes in Octopus Server 2019.6.2

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

Changes in Octopus Server 2019.6.1

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

Changes in Octopus Server 2019.6.0

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

Changes in Octopus Server 2019.5.12

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

Changes in Octopus Server 2019.5.10

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

Changes in Octopus Server 2019.5.9

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

Changes in Octopus Server 2019.5.8

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

Changes in Octopus Server 2019.5.7

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

Changes in Octopus Server 2019.5.6

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

Changes in Octopus Server 2019.5.4

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

Changes in Octopus Server 2019.5.3

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

Changes in Octopus Server 2019.5.2

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

Changes in Octopus Server 2019.5.1

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

Changes in Octopus Server 2019.5.0

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

Changes in Octopus Server 2019.4.5

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

Changes in Octopus Server 2019.4.4

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

Changes in Octopus Server 2019.4.3

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

Changes in Octopus Server 2019.4.2

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

Changes in Octopus Server 2019.4.1

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

Changes in Octopus Server 2019.3.8

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

Changes in Octopus Server 2019.3.7

  • 5737 - Fixed issue where proxy password was in certain circumstances rendered as clear text in deployment log CVE-2019-14268

Changes in Octopus Server 2019.3.6

  • 5453 - Introduced table caching of user details in server, to address performance issues
  • 5627 - Fix for TypeError on certificate search, when certificate data was in an unexpected state
  • 5633 - Further fixes for boolean handling in the Azure Resource Group template step UI
  • 5670 - Fixed issue where historical feed data in database caused primary key violation when creating a new space
  • 5690 - Fix for Tenant variablesmissing endpoint is slow to load with a project/tenant filter when there are many tenants variables
  • 5700 - Fix for Upgrading from 2018.10 to 2019.3+ fails when package configuration contains forward slashes
  • 5702 - Fix for incorrectly migrated user roles that could not be saved due to validation error

Changes in Octopus Server 2019.3.5

  • 5615 - More defensive error handling when docker acquisition fails

Changes in Octopus Server 2019.3.4

  • 5553 - Improve Performance of Dashboard by indexing temp table
  • 5565 - Azure Resource Group step fixed to handle the templates correctly when bool and integer types are used
  • 5571 - Fixed bug that caused automatic release creation failures to return 400 and 500 on package push
  • 5576 - Fixed high CPU usage on deployment task page
  • 5580 - Resolved issue where certificates with private keys were being shown as not having a private key

Changes in Octopus Server 2019.3.3

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

Changes in Octopus Server 2019.3.2

  • 5457 - Improved the speed of the automatic release creation after a package upload
  • 5516 - Automatic Release Creation now creates releases after a step rename
  • 5517 - Fix up some UserRoles that were not set up correctly in 2019.1 and could not be saved
  • 5433 - Update to Halibut to ignore unnecessary ACL failures that were causing deployments to fail
  • 5529 - Fixed an access control bug where project scoping was not being applied for VariableViewUnscoped and VariableEditUnscoped permissions (CVE-2019-11632)

Changes in Octopus Server 2019.3.1

  • 5446 - Fix for users seeing a blank screen when they were set up with no permissions
  • 5454 - Improved the performance the Projects API when many projects use features that are based on step names
  • 5459 - Auto Release Creation and Scheduled Triggers can now create releases for projects using Step Templates that reference packages other than the one uploaded. Improved the speed of the Machine status triggered AutoDeploy

Changes in Octopus Server 2019.3.0

2019.3 LTS

Changes in Octopus Server 2019.2.8

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

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

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

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

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

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

Changes in Octopus Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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-&gt;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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 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 Server 2018.7.6

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

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

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

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

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

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

  • 4591 - Fix for a timing problem that was causing browser redirect issues on slow connections

Changes in Octopus Server 2018.5.3

  • 4480 - Improved long path support, including package extraction and offline drops, see https://octopus.com/docs/deploying-applications/custom-scripts/long-paths for more details
  • 4528 - Allow password to be passed as parameter to offline-drop scripts
  • 4582 - Viewing of Library Variable Sets will now check for VariableViewUnscoped instead of incorrectly checking for VariableEditUnscoped
  • 4583 - Added project groups to configuration options for dashboard filtering
  • 4584 - Add project dialog updated to guide the user to group and life-cycle selection once there are multiple groups or life-cycles, or there is at least one existing project
  • 4586 - SMTP Configuration save and test action is now available in UI to users with ConfigureServer permission

Changes in Octopus Server 2018.5.2

  • 4541 - Output-variables can now be flagged as sensitive
  • 4555 - Users can now modify tenant Common Variables if they have access to all projects and/or all environments this tenant is connected to with VariableEdit permission
  • 4557 - Resolved issue using version mask in pre-release tag when creating release
  • 4569 - Fixed issue preventing a script console scripts targeting more than one tenant
  • 4570 - Improved task log messages when a server task is blocked by another server task
  • 4578 - Enforce obfuscation in deployment logs of sensitive variables contributed via machines (CVE-2018-11320)
  • 4579 - The built-in repository now applied retention rules to packages that are dynamically referenced

Changes in Octopus Server 2018.5.1

Carried forwards from 2018.5.0:

  • 3637 - Updated Azure SDK dependencies to latest. Updated Azure PowerShell Modules to v5.7.0
  • 3731 - Added warnings about Management Certificates for Azure's up-coming June 30th deprecation deadline
  • 3821 - Restricting Cloud Services to Management Certificate accounts at the API
  • 3860 - Updating Calamari to include latest Azure PowerShell cmdlets
  • 4195 - Updating Calamari to .NET452 for latest Azure ARM templates
  • 4461 - Adding support for uploading and exporting certificate chains in the PEM format
  • 4532 - Updated bundled AWS cli to version 1.15.18
  • 3544 - Automatically uploading certificates for Service Fabric clusters

Specific to 2018.5.1:

  • 4346 - Server retention policy now deletes releases as part of the retention policy task instead of creating a task for each document to be deleted
  • 4426 - Improvements to package and release search UX
  • 4520 - Fixes an issue in using inline Terraform templates
  • 4527 - Fixes an issue preventing Terraform steps running on external workers
  • 4535 - Fixes an issue preventing AWS S3 steps running on external workers
  • 4536 - Fixes an issue in using AWS CLI step on external workers
  • 4554 - Refactored Calamari to support multiple authentication contexts
  • 4556 - Fixed an issue introduced in 2018.5.0 which prevented including/excluding specific deployment targets in a deployment

Changes in Octopus Server 2018.4.12

  • 4391 - Fixed error causing tentacles to remove tenanted mode when registered multiple times from the command line
  • 4545 - Tomcat network timeouts increased to 5 minutes

Changes in Octopus Server 2018.4.11

  • 4526 - Fix issue where local project variables weren't shown for both terraform and cloud formation templates
  • 4534 - Fixed timezone conversion issue with weekly & monthly scheduled triggers

Changes in Octopus Server 2018.4.10

  • 4439 - Fix a bug where Project Switcher highlights the entire container rather than the selected project
  • 4523 - Resolved issue with automatic-release-creation when project contains a Deploy Release step
  • 4529 - Fix for incorrect start time shown on Scheduled Project Trigger summary

Changes in Octopus Server 2018.4.9

  • 4486 - Fixed a problem which prevented you from deleting/revoking an API Key which was introduced in 2018.1.0

Changes in Octopus Server 2018.4.8

  • 4524 - When debugging Octopus Variables as part of a deployment, the variables are now printed in alphabetical order by name instead of the order they are added to the variable dictionary
  • 4525 - Fix issue where CloudFormation step wasn't properly registered in the UI

Changes in Octopus Server 2018.4.7

  • 4454 - Fixed a security hole where target and tenant tag variable scopes were not checked against the list of tenants the user has access to (CVE-2018-10550)
  • 4474 - Fix a bug where users without VariableEdit permission can save tenant variable (CVE-2018-10581)
  • 4517 - Fixed a bug where conversion from Sensitive variable type to Certificate variable type was broken
  • 4522 - Fixed error when a new pipeline step resumes from manual intervention

Changes in Octopus Server 2018.4.6

  • 4506 - Fixed timezone conversion issue with scheduled project trigger start time
  • 4512 - Offline Drops now escape script parameters, fixing a bug introduced in 2018.3.8

Changes in Octopus Server 2018.4.5

  • 4468 - The Tentacle included in this release registers faster when the Octopus Server has many environments or tenants
  • 4503 - Fix S3 Package.FileName output variable not set

Changes in Octopus Server 2018.4.4

  • 4498 - Removed parts of the old deployment pipeline, as well as the Octopus.Action.UseNewExecutionDispatcher variable
  • 4505 - Compatibility fix for Offline Drop output variables on PowerShell 2
  • 4507 - Regression in Terraform destroy step is resolved
  • 4510 - Removed -var-file options from terraform init command

Changes in Octopus Server 2018.4.3

  • 4489 - Deep links containing filters are preserved correctly across the login process
  • 4494 - Use FQDN examples for built-in repository examples
  • 4495 - Fixed a problem where run-on-server-on-behalf-of scoped AWS and Azure steps would sometimes run on the target instead of the server
  • 4499 - The IIS, Windows Server, Terraform and VHD steps now use the new pipeline
  • 4501 - Fixed migration that was deleting library variable snapshots even when they were still in use
  • 4502 - Resolved exception when a null variable is defined as a CloudFormation output
  • 4504 - Fixed an exception in the Configuration, Settings page

Changes in Octopus Server 2018.4.1

  • 4178 - The built-in repository can now delete unused packages that are dynamically referenced. See the details of this issue for instructions on how to enable this feature
  • 4393 - Offline drop now only includes each package once per release
  • 4456 - Individual variable files can now be listed in the Terraform step, and the apply and init terraform actions can have additional arguments passed to them
  • 4471 - Added tenant selector for running ad-hoc scripts per tenant
  • 4477 - The permission required to delete users has been relaxed from AdministerSystem to UserEdit, with the caveat that you cannot delete yourself, and only System Administrators can delete other System Administrators
  • 4479 - Fixed SQL error when using taskState in deployments API
  • 4481 - Octopus.Action.Terraform.CustomTerraformExecutable can be set to the location of a customer terraform executable
  • 4483 - Task details page doesn't crash anymore when the log contains PowerShell code that invokes a static method
  • 4485 - Improved performance in reading the stream from SSH targets
  • 4488 - The Server Extensibility API has changed and custom extensions will need to be updated
  • 4490 - Convert OfflineDrop Write-Host to Write-Output in bootstrapper
  • 4491 - Resolved a step execution performance issue when there are lots of variables that was introduced in 2018.3.8
  • 4493 - Terraform updated to 0.11.7

Changes in Octopus Server 2018.4.0

  • 4335 - Breaking change Automatic release creation now selects packages appropriate for the channel the release is created in
  • 3633 - Added a new project trigger for recurring scheduled deployments
  • 4365 - Deployment Steps can be marked as required, meaning they cannot be skipped when customizing a deployment
  • 4422 - Fixed a problem where Variable Sets were deleted even when they were used by existing releases
  • 4433 - Release version search in Deploy a Release now displays Load More
  • 4448 - Fix for error when filtering Tenants and user does not have view permissions for some Environments
  • 4463 - Fix for show and hide empty groups on Project dashboard
  • 4473 - Fixes for “Deploy To” button popover on mobile
  • 4482 - Added the new AWS S3 upload step for uploading files to an S3 bucket with all the bells and whistles

Changes in Octopus Server 2018.3.13

  • 4445 - Various accessibility updates and improvements to the UX (and fixing broken avatar images on closed networks)
  • 4451 - Fixed a performance problem in Variable Editor where rendering of variables with a lot of values was slow
  • 4464 - HCL parsing logic moved into separate open source library

Changes in Octopus Server 2018.3.12

  • 4399 - Fixed error when viewing tenant variables if user lacked permission to see other associated environments
  • 4449 - Fixes an error that stopped users from health checking all environments they had permission to
  • 4455 - Update Terraform to 0.11.6
  • 4460 - Variable replacement occurs for scripts sourced from packages, fixing a bug introduced in 2018.3.8
  • 4462 - Scripts sourced from packages are no longer executed with incorrect arguments, fixing a bug introduced in 2018.3.8

Changes in Octopus Server 2018.3.11

  • 4452 - Fixed an error loading variables, step templates and script modules when there are many machines

Changes in Octopus Server 2018.3.10

  • 3690 - We warn user now when they select a cert file that is empty
  • 4147 - Lists with parameters can now be manually ordered
  • 4220 - Dashboard filters are now stored in the query string in the URL
  • 4330 - Fix a bug where deployment process page crashed if there is an IIS step that has no bindings
  • 4382 - Do not open new window when clicking on links in task log page
  • 4398 - Library variable set filter when including a library variable set in a project is now case insensitive
  • 4432 - When using the service command to start and stop the Octopus Server service and the service does not exist, Octopus and Tentacle will now report an error
  • 4443 - Improved performance when validating tenant connections
  • 4444 - The variable editor now only warns on specific zero width characters, and no longer has false positive warnings for non-ASCII characters
  • 4447 - Fix for events/audit not being returned when user had scoped permissions applied

Changes in Octopus Server 2018.3.9

  • 4118 - Switched from 4 to 2 spaces for list indentation in markdown
  • 4203 - Fix for issue where when filtering projects or dashboard would cause the header title to disappear
  • 4397 - Fix a bug where project variables are not showing in Run a Docker Container step
  • 4401 - The Secure flag is now set consistently for Cookies regardless of whether the incoming HTTP request is behind a proxy using SSL offloading
  • 4428 - Certificate expiry events are now generated for a certificate that has replaced another certificate if the original certificate had either of the certificate expiry events created
  • 4431 - AWS steps now acquire packages correctly when used as child steps
  • 4441 - The OctopusBypassDeploymentMutex now does what it is supposed to do, fixing a bug introduced in 2018.3.8
  • 4175 - Fixed display issue on Project descriptions that have markdown

Changes in Octopus Server 2018.3.8

  • 4291 - Swagger spec now takes virtual directories into account
  • 4354 - Package notes now show if they are missing, or if the notes can not be retrieved
  • 4361 - Fix a bug where dashboard environment scrollbar loses its position when data updated
  • 4419 - Fixed broken links to triggers and channels in the audit log
  • 4420 - Implemented a new deployment pipeline which lays the groundwork for future features. It is enabled for Run Script, Deploy Package and Run AWS Script steps
  • 4421 - The Step Template -> Run feature now treats sensitive parameters correctly instead of passing them to the server as clear-text
  • 4423 - Support Output Variables for Offline Drop
  • 4424 - Insert variable doesn't throw an error when filter contains regex characters
  • 4429 - Fixed up the package acquisition for AWS CloudFormation steps when workers are used

Changes in Octopus Server 2018.3.7

  • 4405 - Release creation page combines requests for the same package + channel filter combination
  • 4407 - Fix a bug where users can see machines beyond their team’s scoped environments in variable editor - CVE-2018-9039
  • 4410 - Default the GitHub Feed url with public GitHub api endpoint
  • 4413 - Updated Terraform executable to 0.11.5
  • 4414 - Fixed the parameters file used when deploying cloudformation templates from a package

Changes in Octopus Server 2018.3.6

  • 4402 - A 400 Bad Request error with reason in response body instead of a 500 Internal Server Error is now returned when trying to create a release on a disabled project
  • 4408 - Added additional logging when a TaskCanceledException is thrown
  • 4409 - Fixed configuration migration issue when upgrading from 3.x
  • 4083 - No longer displaying two horizontal scrollbars in project dashboard
  • 4260 - Admin command line now supports adding groups from Active Directory, and groups/roles from AzureAD and Okta
  • 4306 - Administrators can now control whether users are allowed to edit their own external Logins
  • 4331 - Password required validation no longer appears when creating service account users
  • 4342 - Group claim handling fixed in the Okta and Azure AD authentication providers
  • 4348 - Added steps for planning to apply or destroy Terraform templates
  • 4360 - Fixed bug causing exceptions for offline drops when path is too long
  • 4364 - Teams with EventView scoped to Projects will not receive Subscription output
  • 4376 - "Prompt for value" checkbox in the variable editor is working again
  • 4377 - If you lose your master key you can now use the Octopus.Server.exe lost-master-key command to generate a new master key, scrub all your sensitive data, and get back up and running again
  • 4378 - It is no longer possible to select an invalid value for a certificate variable
  • 4379 - Project ID in Deploy Release step is now correctly mapped when migrating
  • 4380 - Variable channel scopes are now correctly mapped when migrating
  • 4381 - Github external feed testing and object reference null error
  • 4387 - Github feed trailing whitespace
  • 4395 - Checkbox-type variable templates now correctly display default values

Changes in Octopus Server 2018.3.4

  • 4363 - Fixed a bug with row heights in the project overview
  • 4375 - Fixed an exception when a user signs out

Changes in Octopus Server 2018.3.3

  • 4269 - Sort deployment targets by name during rolling deployments so the deployment order is deterministic
  • 4309 - Fixed an issue where the tenants page may sometimes fail to load when there is a large number of projects
  • 4366 - Fixed exception when downloading packages with 4 part version numbers on SSH targets without mono
  • 4367 - Fix for errors incorrectly showing user lacks VariableEdit if that permission was scoped to Projects
  • 4368 - Permanently enabled the Docker and Browser Caching features, and multi-tenancy is enabled when a tenant is first created
  • 4370 - Increased network timeouts when interacting with Tomcat from 30 to 60 seconds
  • 4371 - Terraform steps now include a field to allow a workspace to be defined

Changes in Octopus Server 2018.3.2

  • 4369 - Fixed a bug where the dashboard would repeatedly request all releases from the Octopus server, and adversely impact performance

Changes in Octopus Server 2018.3.1

  • 4119 - Fixed problem with Variable Editor creating values that can't be saved
  • 4218 - Audit log filtering would error in some cases and this is fixed now
  • 4234 - Ensuring we can render old releases in project overview
  • 4264 - A new log level Highlight has been added that highlights the message in the log and shows it on the Task Summary tab
  • 4275 - Fixed a bug where in some situations, the read only table of variables would extend beyond the available screen width
  • 4300 - Added an upgrade script to clean up orphaned channel version rules
  • 4307 - Fixed subscriptions and web hooks that were not firing for users who had scoped permissions
  • 4308 - Fixed issue when upgrading a system with an Octopus Managers team
  • 4312 - Fixed issue with the AzureAD authentication provider sometimes getting a signature error while validating tokens
  • 4314 - Release page navigation links now work regardless of whether the current URL contains a trailing slash
  • 4316 - Open markdown links in a new window
  • 4322 - Fixed a bug where the tenant tags would be pre-filled on the create deployment page if you had navigated to a create deployment url for deploying to specific tenants
  • 4326 - Stop showing a delete option in the UI if you don't have access to view a particular user
  • 4332 - Additional error logging is generated for network errors when deploying CloudFormation templates
  • 4333 - Fixed error in queueing tasks when 1000's of tasks are ready to run
  • 4336 - Add #{else} to the existing #{if} statement in the variable substitution syntax
  • 4337 - Artifacts now appear under the step heading on the Task Summary page
  • 4339 - Add terraform apply and destroy steps
  • 4344 - Cloudformation dynamic variables form does not recognise specilised lists
  • 4345 - Cloudformation step will exit early if there are nested stacks
  • 4347 - Fixed a bug where the environments filters would disappear if no environments matched the current filter
  • 4351 - Fixed an issue where searching through certificates might fail for some types of certificates
  • 4352 - Removed redundant call to /api/projects/all from getting-started component
  • 4353 - Fixed metrics logging to not use quotes around numbers
  • 4356 - Added a field to allow additional files to have variable substitution applied to them from Terraform packages
  • 4357 - Additional file extensions are now downloaded from Maven repositories
  • 4358 - Null reference exception removed when the AWS region is incorrect
  • 4359 - Fix for the error about missing EventView permission on the release page when it is scoped to Projects

Changes in Octopus Server 2018.2.8

  • 4311 - Removed the MaxParallelism of 10 for steps - Octopus will run an unlimited number of steps at the same time if you configure your deployment process this way
  • 4338 - Add aes256-ctr to the list of allowed SSH ciphers when in FIPS mode

Changes in Octopus Server 2018.2.7

  • 3441 - Each Octopus server node may execute one (non deployment or health check) task beyond its task cap, so that tasks such as subscriptions are not blocked by long running deployments or health checks
  • 3475 - Use octopurls for documentation urls
  • 3556 - "MaxConcurrentTasks" is now the sum of all server node's task caps. Command option Octopus.Server.exe configure --maxConcurrentTasks ... is deprecated
  • 4088 - Tentacle auto-upgrades are now blocked for a machine that is being auto-deployed to
  • 4168 - Tasks are allocated more evenly to Octopus server nodes in High Availability Octopus
  • 4281 - Displayed the deployment start time instead of the queued time on the dashboard and release pages
  • 4289 - Deploy Release step task log now includes link to child deployment
  • 4295 - Only run autocomplete hack for Chrome on Sign-In screen
  • 4298 - CloudFormation steps now populate the proxy configuration
  • 4303 - Correctly handle missing deployments when processing auto deploy events
  • 4305 - Disabled child steps can no longer have a duplicate name
  • 4310 - Fixed an error on the Release Detail page when a user does not have TaskView permission
  • 4125 - Improved log message when importing certificate-chain which already exists
  • 4163 - User login bans, due to too many failed attempts, now appear in the Audit log
  • 4197 - Update our SSH library so that it works on Octopus servers with FIPS enabled
  • 4315 - Explicitly reject all HTTP TRACE requests rather than treating them as a GET in some cases
  • 4317 - Tenanted deployments will always be executed in the order that they appear in the task queue
  • 4318 - Account Edit page now loads usage data asynchronously to avoid blocking the UI
  • 4320 - Default values on Tenant Variables are not displayed on V4 Variable Editor
  • 4321 - Fix for TypeError: Cannot read property 'State' of undefined on Release page, for users with TaskView permissions scoped to Environments
  • 4323 - Added metrics command for configuring metrics logging
  • 4324 - Fixed High CPU usage when there are not tasks in the queue or the node is in maintenance mode
  • 4325 - "Deploy a package" step now has access to Maven feeds
  • 4329 - Removed the word "anonymous" from the installation wizard's consent to collect usage data - the word "anonymous" was mistakenly added in Octopus 3.12.0

Changes in Octopus Server 2018.2.5

  • 4285 - Reducing reflow of dashboard status tables to improve performance
  • 4292 - Disabling keyboard form submissions on Script Console / AdHoc script
  • 4294 - Bring back predictable order to the Add Step page
  • 4296 - Fixed a deployment error when using script modules with paths that have ' in them
  • 4297 - Improve the database indexes used during auto deploy creation
  • 4299 - Fixed bug introduced in 2018.2.0 that caused Calamari upgrade to loop indefinitely if the customBundledPackageDirectory option is used

Changes in Octopus Server 2018.2.4

  • 4131 - Fix a bug where Deploy to button is missing from the Task page
  • 4132 - Excluded steps are now preserved between retries
  • 4142 - Fixed a problem where teams scoped to an environment couldn't add project variable templates
  • 4231 - Now you can add an environment to a lifecycle phase without having EnvironmentCreate permission
  • 4245 - Added inline note that explains when tenanted deployments are available
  • 4246 - Code editor full screen toggle no longer overlays scrollbar
  • 4254 - Custom Install Directory feature shows now correctly whether files will be purged or not
  • 4259 - Don't specify /bin/bash when performing a raw file transfer to an SSH target
  • 4273 - Prevent child releases to many tenants exhausting the task cap
  • 4280 - Fixed text-wrapping behaviour in long section titles
  • 4282 - Allow channel version rules based on deploy release steps
  • 4283 - Variable Template heading displays now Label instead of Name when Label is available
  • 4284 - Azure account scoped to both tenanted and untenanted can now deploy to untenanted deployments
  • 4286 - Prevent the deploy release step from being added as a child step
  • 4288 - Fixed UI issue where changing settings asked for AdministerSystem permission instead of ConfigureServer
  • 4290 - Reduce strictness of package filename encoding to allow + characters in path

Changes in Octopus Server 2018.2.3

  • 4250 - Project name is now a link (when not bound to a variable)
  • 4271 - Added metric logging to track api calls and tasks
  • 4276 - Resolved error when creating release for projects containing a Deploy Release step

Changes in Octopus Server 2018.2.2

  • 4202 - Package selector and Release selector are not showing double scrollbars anymore
  • 4233 - Added validation to ensure that Deploy to IIS steps include package details
  • 4248 - Powershell AWS modules are now exposed to the AWS CLI script step
  • 4262 - Fix a frontend crash when the project dashboard can't find the channel for a dashboard item
  • 4263 - Fixed a bug which prevented variable value from being displayed in the variable editor popup
  • 4267 - Fix a frontend crash on the project triggers page when an invalid ARC step is selected
  • 4268 - Allow prompted variables in child deployments to be bound from variables on the parent
  • 4272 - Fix bug causing channels with version rules to sometimes not auto-select latest package

Changes in Octopus Server 2018.2.1

  • 3494 - When scrolling through many environments in project overview, the releases column is now fixed
  • 3900 - Fixed missing audit entry when a variable scoped to a single environment and that environment is deleted
  • 3930 - Fixed role deletion mechanism, it will now be removed from teams that were referencing it, after the user is shown a warning
  • 3980 - Add account usage UI to /infrastructure/accounts/[account]
  • 4114 - Packages API does not meet the requirements of our expanding feed types
  • 4176 - Projects overview table first column is now fixed width
  • 4180 - Added new step: Deploy a Release
  • 4211 - Modify the cache naming format to allow for new feed formats
  • 4216 - Added additional steps and account types to support AWS scripts and CloudFormation deployments
  • 4222 - Fixed a bug where deleting a channel could result in orphaned channel version rules and break the project dashboard
  • 4238 - Fixed a bug with incorrect target counts on the infrastructure dashboard under tenant target sets
  • 4239 - When AutoDeployLastProcessedEventAutoId is null Octopus attempts to process all previous events
  • 4255 - 2018.2 Bug Bash Feeback: Delete Account
  • 4257 - Fixed permission issue where users deploying a project they had permissions for would fail

Changes in Octopus Server 2018.1.5

  • 4208 - Fixed issue where task creation required higher level permissions than needed
  • 4225 - The built-in repository can now be configured by a user with the ConfigureServer permission instead of requiring the AdministerSystem permission
  • 4235 - All nodes can now be drained at the same time
  • 4242 - Scrollbars are restored after using code editor in fullscreen

Changes in Octopus Server 2018.1.4

  • 4123 - Package Acquisition no longer fails with a Object reference not set error when multiple deployments attempt to access the package cache
  • 4189 - Ensure the artifact list does not reset when the page auto-refreshes
  • 4196 - Octopus.Machine.Hostname system variable is now available on transient target
  • 4199 - Fix a bug where ‘Include Library Variable Sets’ in Project Library Sets page deselects existing Library Variable Sets when opened before Sets are rendered
  • 4201 - Run-on-server script steps can now be run on a Tentacle that runs a under a different user account
  • 4212 - The project dashboard release filter can now be specified by version number in the query string
  • 4226 - Making deployment target discovery UI more intuitive
  • 4232 - Replaced the Start Mode section in the IIS deployment step with bindable checkboxes in the Web Site and Application Pool sections

Changes in Octopus Server 2018.1.3

  • 4137 - Allow configuration of LicenseNotificationMode via configure command
  • 4179 - Fixed issue where tag sets re-order feature is missing from the portal
  • 4184 - When collecting an artifact using New-OctopusArtifact, we now allow other processes to access the file
  • 4207 - Fixed issue where updating Calamari required higher permissions than necessary
  • 4217 - Add Feed button not visible without AdministerSystem permission
  • 4224 - Fixed a bug in JsonEscape variable substitution filter
  • 4182 - Fixed issue where manual intervention instructions couldn't be bound to a variable

Changes in Octopus Server 2018.1.2

  • 4213 - Database upgrade licence check now detects pre-3.4 versions and is skipped
  • 4214 - Fixed the validation error when a variable is used for authentication method in the IIS step

Changes in Octopus Server 2018.1.1

  • 4204 - Add configuration setting to enable long path support in Calamari.Azure
  • 4206 - Fixes an issue introduced in 2018.1.0 that prevents IIS steps from being saved if the website or app pool name fields use a variable binding expression

Changes in Octopus Server 2018.1.0

  • 3317 - When installing Octopus Server and using a Custom Windows Account to run the service, the installation wizard will configure SQL Server correctly so the Custom Windows Account can access the database
  • 3924 - Auto machine removal now happens as part of health checks. Minor breaking change API endpoint for machine removal logs is removed and machine removal logs are no longer stored on the Octopus server
  • 3974 - Steps may now be explicitly configured to run before or after package acquisition
  • 4070 - The built-in worker, which executes deployment steps and scripts on the Octopus Server, can now be configured to run using a different, lower-privileged user account
  • 4143 - Fix for infrastructure overview not correctly flowing tag sets from associated tenants
  • 4144 - Import using the Octopus migrator finds the correct deployment process for scripts from similarly named projects
  • 4157 - Existing orphaned channels and releases are removed from the database
  • 4183 - The check to see whether a step template is in use is now much quicker
  • 4185 - Environments, channels and tags now cannot be deleted if they are used by a disabled step in a project's current process
  • 4192 - Package notes are fetched in bulk and in async, meaning a release can be deployed without all notes being downloaded first
  • 4194 - The installed version of Octopus Server is now tracked to help us provide support when data issues occur and is a precursor to raising and event on upgrade

Changes in Octopus Server 4.1.10

  • 2668 - The database upgrade now checks whether the licence would be non-compliant after upgrade and aborts the upgrade in order to prevent getting stuck with an expired licence and not being able to deploy
  • 3454 - Digitally signed Octo.exe and Octopus.Clients.dll so that AV respects it more
  • 3802 - Added support for passing password on the commandline to docker login
  • 3910 - Added option to filter by phase name in lifecycles page
  • 4040 - Minor breaking changes Project and tenant name cannot include unsupported file system characters
  • 4102 - Now we only test the connection to the master database when creating or deleting the Octopus database, which in turn fixes a problem we introduced in 4.1.0 with upgrading Octopus in certain situations
  • 4130 - PowerShell script parameters with a trailing slash no longer break script execution
  • 4155 - Fix a bug where metadata component in release version is not working with SemVer 2.0 template
  • 4162 - Added the ability to prevent package scripts from being run by specifying the Octopus.Action.Package.RunScripts variable and setting it to false
  • 4165 - We no longer attempt to deploy packages when acquisition fails
  • 4169 - Fix for deployment process screen where viewing email step that references a deleted team
  • 4171 - Don`t show username for external groups in teams area
  • 4174 - Dynamic package feeds now working again with channel rules
  • 4187 - Check for $JAVAHOME now uses [[ -n "${JAVAHOME}" ]] instead of -v to support older versions of bash

Changes in Octopus Server 4.1.9

  • 3827 - Fix a bug where tasks with manual intervention are listed as the queued behind tasks on Task page
  • 3913 - Increased number of possible PowerShell variables in scripts to maximum available
  • 3963 - Corrected the help message explaining what a valid version number looks like
  • 3990 - Increased contrast of form elements and content hierarchy
  • 4032 - Validate that environment and project ids exist when creating or modifying tenants
  • 4072 - Swagger documentation now works if Octopus is running in a virtual directory
  • 4085 - Improved the performance of the project Library Variable Sets page when there are many variable sets
  • 4087 - Fix a bug where task summary does not show on Task page when it is waiting for manual intervention
  • 4090 - Selecting a single date on the Audit page now shows the correct date range
  • 4146 - Prevented the filter panel from opening when you set a quick filter
  • 4161 - Improve performance of tenant variables when large number present
  • 4164 - UI data refresh is now triggered almost immediately after a tab becomes active again if it has been longer than the normal refresh interval; The refresh will also occur if the tab is in the background at a 12th the normal rate
  • 4167 - Fixed a security vulnerability where incorrectly configured user roles and teams would allow members of those teams to escalate their own permissions - Octopus now actively prevents any user from escalating their own effective set of permissions - CVE-2018-5706