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.6.8 to 2019.9.1

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.

Release notes

These are the features and fixes you'll get by upgrading from 2019.6.8 to 2019.9.1.

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