Compare releases

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

→

What's new

These are the most important features you'll get by upgrading from 2019.3.5 to 2019.6.3

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.

Release notes

These are the features and fixes you'll get by upgrading from 2019.3.5 to 2019.6.3.

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

  • 5615 - More defensive error handling when docker acquisition fails