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 2022.1.3072 to 2022.3.7783-hotfix.8765

Octopus 2022.3

As organizations continue to modernize, it's becoming increasingly important to ensure you can safely and reliably audit your CI/CD pipelines. You need to monitor and secure your deployments, and your teams need to scale reliably with tools to collaborate as releases move from deployment to testing and production.

This release adds support for version-controlled variables for version-controlled projects for a more complete implementation of the Config as Code solution we released in March. We also have several other new features to help you build safe, reliable, and auditable “As Code” CI/CD pipelines. These include ITSM change management with our ServiceNow and Jira Service Management integrations and built-in DevOps reporting.

This release’s noteworthy updates include:

  • Config as Code - version-controlled variables for version-controlled projects
  • ITSM - change management without friction for ServiceNow
  • Jira Service Management - efficient change management approvals (early access)
  • DevOps Insights - DORA insights to quantify value and improvements (early access)
  • GitHub Actions for Octopus Deploy v2
  • Simpler cloud target discovery setup

Together, these features support collaboration, scalability, and security for your deployments.

The 2022 Q3 release is available on Octopus Cloud and ready for download by our self-hosted customers.

Octopus 2022.2

Moving to cloud-native isn’t about randomly lifting and shifting every component or rewriting every application. It's about combining the right technologies and tools and making strategic choices about where to modernize and where to maintain.

Whether you're deploying to AWS, Azure, GCP, or your own data center - wherever you are on your cloud journey - Octopus Deploy is the only deployment tool you'll ever need.

We’re improving our cloud-native support with new features to help you containerize and modernize your CI/CD pipeline. We improved support to deploy containerized applications to Amazon ECS and Kubernetes, added the cloud target discovery feature, and made serverless improvements for AWS.

The 2022 Q2 release is available on Octopus Cloud and ready for download by our self-hosted customers.

This release also includes other noteworthy updates:

  • ServiceNow Change Management without the friction (early access preview)
  • Config as Code usability improvements to release creation and step templates
  • Faster Octopus Cloud deployments with better Dynamic Worker caching
  • Customer-driven updates:
    • Easy customization of Project and Space icons
    • Improved security administration with adjustable session timeouts and invalidation
    • Support for OAuth 2.1 Authorization Code flow with PKCE
    • Tenant variable versioning without errors

Octopus 2022.1

Highlights

Configuration as Code (Config as Code) for deployments is now available! This means you can see your deployment process in your Git repo next to your application code and evolve them together. When Config as Code is enabled for a project, you can continue to use the Octopus UI as you always have, or you can edit the text files in your favorite editor. Work wherever you're the most productive.

This release also includes other noteworthy updates:

  • Visual Studio Code extension with Octopus Configuration Language (OCL) syntax highlighting, code snippets, and navigation tree
  • Updated Terraform Provider with support for version-controlled projects
  • New integrations:
    • Buildkite plugins (early access) allow your build agents to create and deploy releases, push build information, and run runbooks as part of a pipeline
    • Opsera integration lets you connect Octopus to other DevOps tools with no-code automation
    • Octopus now supports connecting to multiple Azure DevOps organizations
    • Updated TeamCity plugin with the latest Log4j security patches
  • Automated step updates and discovery for steps built using our next-generation step package framework
  • Octopus Deploy acquired the Dist technology

Breaking changes

This release contains one breaking change.

Config as Code API URLs renamed

We have made minor changes to some Config as Code API URLs and keys in the related links collection. These changes only impact version-controlled projects and should only cause issues if you're using any URLs directly.

Learn more about this change in the GitHub issue.

Release notes

These are the features and fixes you'll get by upgrading from 2022.1.3072 to 2022.3.7783-hotfix.8765.

Changes in Octopus Server 2022.3.7783-hotfix.8765

  • 7722 - Fixed an issue where reading package references from OCL could result in a “Resource not found” error

Changes in Octopus Server 2022.3.7782

  • 7662 - Repairing malformed Build Information events. Azure SQL users: consider temporarily scaling your DTU count up if you have lots of rows in the Event table. You can scale back down once the upgrade is finished
  • 7704 - Fixed an issue where Deploy a Release would block OCL migrations

Changes in Octopus Server 2022.3.7274

  • 5677 - All the queued server tasks are displayed when deploying for a project with a pending manual intervention task.
  • 7704 - Fixed an issue where Deploy a Release would block OCL migrations
  • 7051 - Typing 'Releases' in Search and selecting 'Octopus Server Releases (builtin)' errors out
  • 7697 - Improved error messages when git migrations fail due to broken references
  • 7700 - Fixed an issue where a FeedId has unknown slug error would appear when reading package steps from OCL
  • 7698 - Removed stack traces from the system report to fix an issue where the instance could crash when downloading such report
  • 7690 - Reduced number of ids per request when retrieving resources via /all?ids
  • 7656 - Cloud target discovery steps will now use the run condition of the step that triggers discovery
  • 7537 - Fixed an issue where changing the default branch in a config-as-code project could result in a cannot delete branch refs/heads/master error message
  • 7571 - Improve EventRelatedDocument population
  • 7681 - Fixed an issue where a Nevermore error would be shown if logging in with OAuth took longer than 30 seconds
  • 7636 - Improved performance of searching packages from external Maven feeds
  • 7663 - Fixed an issue where Health Checks for Azure App Service targets failed for clouds other than Azure Public (eg Azure Government)

Changes in Octopus Server 2022.3.5513-hotfix.7091

  • 7704 - Fixed an issue where Deploy a Release would block OCL migrations

Changes in Octopus Server 2022.3.5512

Breaking Changes
  • 7673 - Reduced number of requests made to external feeds when creating and viewing releases. SelectedPackagePublished in deploymentprocesses/{id}/template has been moved to Published in packages/notes
Other Changes
  • 7672 - Fixed an issue where the releases/create/v1 endpoint would fail to create releases for version controlled projects with package references
  • 7675 - Fix error viewing a release when a lifecycle phase has trailing whitespace
  • 7551 - Tenant Tags correctly filter deployment targets on Infrastructure screen (regression)
  • 7670 - Fixed warning message: Resolving ... from this named scope OctopusTaskScope is not permitted
  • 7666 - Improved performance of retrieving and deleting artifacts
  • 7658 - Added a retry policy with exponential delay when fetching the message bus sequence number to avoid logging too many messages
  • 7661 - Fixes an issue where Octopus Cloud and Octopus Server on Linux could not talk to NuGet feeds hosted behind NTLM auth (including self-hosted TFS package feeds)

Changes in Octopus Server 2022.3.4954-hotfix.5455

  • 7672 - Fixed an issue where the releases/create/v1 endpoint would fail to create releases for version controlled projects with package references

Changes in Octopus Server 2022.3.4953

Breaking Changes
  • 7645 - Update OCL to reference shared resources via slugs instead of names. Update API responses for version-controlled documents to reference shared resources via IDs instead of names
Other Changes
  • 7640 - Fix triggers not processing when a space's task queue is stopped
  • 7657 - Fixed an issue where step templates with broken references could prevent deployment processed from being read from OCL
  • 7644 - Improved performance of viewing variable sets
  • 7653 - Updated Create Release/Execution commands JSON payload definitions to match its associated class properties
  • 7652 - Address a performance issue when using step templates in a version controlled deployment process
  • 7770 - CaC Long file paths Error
  • 7648 - Fixed an issue where step packages stored in OCL were incorrectly deserialised
  • 7632 - Added the ability to specify a docker network name in the docker create a network step
  • 7635 - Improve performance of deploymentprocesses/template
  • 7634 - Scheduled trigger times are correctly shown and new triggers execute as expected
  • 7642 - Fix slow memory leak in Octopus Server
  • 7602 - Runbook multi-tenancy and deployment target status resets to default when cloning a project with runbooks
  • 7615 - Fixed the Build Information event categories on audit events
  • 7603 - Fixed an issue where Run a Kubernetes Script step would fail if the cluster was not available
  • 7628 - Fix issue where not found error was returned when creating releases for Git projects with deploy release actions
  • 7626 - Creating a release in the UI is blocked if using a Docker feed that fails to search (eg. GitHub Container Registry)
  • 7624 - Scheduled Tasks Logs are intermittently missing from the UI but appear in the shared .\TaskLogs folder
  • 7611 - Change how we scan for task logs so we don't enumerate the whole task logs folder which caused performance issues for instances with a large amount of task logs
  • 7545 - Fixed issue with Unicode in project names
  • 7620 - Fix external feed lookup error when using a step template that uses an external feed many times in Git deployment process
  • 7610 - Fix issue where Git projects with step templates are permanently broken after changes are made to referenced data
  • 7546 - Performance telemetry is now logged at a verbose level when send telemetry server task runs
  • 7427 - Fixed an issue where Octopus Server would not start when the license is expired
  • 7544 - Fixed an issue where the configured Web Request Proxy was not respected in Health Checks for Azure App Service deployment targets
  • 7598 - SSH workers will no longer deadlock on parent/child deployments

Changes in Octopus Server 2022.3.2617-hotfix.3946

  • 7642 - Fix slow memory leak in Octopus Server
  • 7634 - Scheduled trigger times are correctly shown and new triggers execute as expected

Changes in Octopus Server 2022.3.2617-hotfix.3276

  • 7628 - Fix issue where not found error was returned when creating releases for Git projects with deploy release actions
  • 7626 - Creating a release in the UI is blocked if using a Docker feed that fails to search (eg. GitHub Container Registry)

Changes in Octopus Server 2022.3.2616

  • 7575 - Fixed an issue where deployments made via automatic lifecycle promotions would fail and remain persisted in a bad state
  • 7428 - Fix issue of YAML editor in Kubernetes step stripping characters from variable whose name contains colons

Changes in Octopus Server 2022.3.2387

  • 6664 - Workers now perform retention on their package cache
  • 7597 - Improve performance of git migration script

Changes in Octopus Server 2022.3.2140

  • 7592 - Add warnings when the SQL connection max pool size is less than triple the task limit/cap
  • 7533 - Limit the amount of releases returned when checking for total number of releases in the Project Overview page
  • 7559 - The health of unavailable SSH targets is once again being recorded correctly

Changes in Octopus Server 2022.3.1591

  • 7589 - Improved the handling of missing steps when using the channel version rule designer

Changes in Octopus Server 2022.3.1456-hotfix.3242

  • 7628 - Fix issue where not found error was returned when creating releases for Git projects with deploy release actions
  • 7626 - Creating a release in the UI is blocked if using a Docker feed that fails to search (eg. GitHub Container Registry)

Changes in Octopus Server 2022.3.1455

  • 7585 - Fix NullReferenceException being thrown when creating or viewing releases with a version mask
  • 5110 - New-OctopusKubernetesTarget command will now validate that one of the following parameters -octopusAccountIdOrName and -octopusClientCertificateIdOrName has been provided
  • 7580 - New-OctopusKubernetesTarget command will now validate that only one of the following parameters have been provided -octopusAccountIdOrName and -octopusClientCertificateIdOrName
  • 7581 - New-OctopusKubernetesTarget command can now set health check container on Kubernetes target that is using certificate authentication
  • 7506 - Fixed the issue where users were unable to deploy to Tomcat via manager over HTTPS
  • 7578 - Fixed an issue where release retention would fail if more than 2100 projects exist
  • 7582 - Fix Unknown Ref Type error showing in the UI after creating a Runbook on a Git project
  • 7579 - Fix issue where action template view permission was incorrectly required when creating releases for processes that used old versions of action templates
  • 7577 - Bugfix for SQL error thrown when creating tenant deployment with a ProjectView permission scoped to 100's of projects
  • 7534 - File and git cache cleanup no longer runs under the task cap
  • 6954 - Package publish datetime in UI inconsistent between Release and Library pages
  • 7562 - Fix whitespace tenant variable values being considered missing
  • 7563 - Fix long tenant variable values being considered missing
  • 7567 - Fixed the Full Table Cache to update stale data that was not detected in some rare conditions
  • 7269 - Improve performance of runbook run preview page when selecting tenants
  • 7553 - Fixed the Full Table Cache to update stale data when rolling back a transaction

Changes in Octopus Server 2022.3.348

Breaking Changes
  • 7375 - Empty versions in Octostache syntax now throw an error instead of returning a default value
Other Changes
  • 7560 - Fix issue where action template view permission was incorrectly required when creating releases
  • 7491 - Improved error message when converting a project to version controlled while a missing reference exists in the deployment process
  • 6774 - Semantic version masks are now correctly evaluated from automatic release creation
  • 7538 - Fixed an issue where creating AD users would always result in a timeout if searching for groups took a long time
  • 7548 - Fixed an issue where orphaned task logs would fail to clean up if a null value exists in OctopusServerInstallationHistory
  • 7600 - Support loading resources and creating releases from commits and tags on Git Projects
  • 7415 - Fixed an issue where collecting machinesbyarchitecture would log a null reference exception
  • 7536 - Fixed an issue where some step templates would incorrectly populate version controlled deployment processes
  • 7456 - Fixed an issue where using the Deploy an Azure App Service step to deploy to a FunctionApp running on a Linux-based AppServicePlan would fail with a Bad Request error
  • 7095 - Fixed an issue where using the Deploy to an Azure App Service step to deploy to multiple App Service targets in parallel would fail due to a file lock
  • 7531 - Fixed inconsistent padding in tenant tag set onboarding page
  • 7076 - "Missing Permission" UI and log warnings for CertificateView and AccountView when viewing Project Variables and Library Variable Sets
  • 7532 - Fixed an issue where task logs with duplicate ids couldn't be cleaned up
  • 7535 - Improve the clarity of the update step template button in version controlled projects
  • 7141 - Octopus now supports OAuth code flow with PKCE when a client secret is specified
  • 7530 - Fixed a bug where the user registration page was unusable because it would always show an error
  • 5831 - Make UI more friendly when editing tenant environments that are no longer in the lifecycles
  • 7035 - Add validation error on deployment settings page - when release versioning from an included package is selected with no package selected
  • 7526 - Active Directory group search is now more resilient to transient errors
  • 7523 - Fixed an issue where packages would be missed when searching in the built-in feed
  • 6249 - Route task links in portal task logs to correct space
  • 7497 - Show detailed Timezone text in portal summary
  • 7516 - Enforce ProjectEdit permissions when editing Git Projects
  • 7446 - Added a note about automatic environments being redundant when a lifecycle phase is set to optional
  • 7490 - Removed related document id check from system integrity check
  • 7419 - LDAP being counted as "non-octopus" authenticator
  • 7482 - Include additional behavioural telemetry for self-hosted instances when opted in
  • 7443 - Fixed an issue where deleting a runbook would result in an error Object reference not set to an instance of an object
  • 7174 - Improve script lock tracking and prevent "task not found" error messages
  • 6526 - Fixed an issue where tenants could not be deleted if a project mapping was removed beforehand
  • 94 - Internal server error (500) when Jira access token is revoked
  • 7469 - Fix code editor full screen behaviour in script console to properly show exit button and scrollbars
  • 7318 - Fixes failing integrity checks related to invalid scoped user role data
  • 7157 - Release page now shows correct start time for deployments
  • 7417 - Octopus Server on Linux will no longer attempt to run HTTP.sys
  • 7444 - Fixed issue with cloud target discovery failing when a manual intervention or email step is in the deployment process
  • 7442 - Fix variable preview page showing 'Variables are not supported in Git' error for Git projects
  • 7364 - Deploy an Azure Resource Manager Template variable Bind for the Account Resource Group doesn't work
  • 7349 - Lock related logs no longer showing in task log
  • 7425 - Fixed an issue where deployment changes were aggregating commits across all releases, but weren't including the commits per release
  • 7036 - Package version now displays correctly on the release details page
  • 7388 - Include process-scoped variables in variable preview
  • 7403 - Removed querying the database for the active transaction count. This fixes an issue where errors would appear in the system log every 30 seconds
  • 7422 - Fixed styling regression for our Code editor component in dark mode
  • 7254 - Parent block in task log marked as done when child is still executing
  • 7306 - Active user sessions can now be revoked
  • 7308 - Session invalidation UI for users
  • 7416 - Fixed an issue where UI styles were undefined causing some screens to misbehave and error
  • 7229 - Lifecycle auto-promotions now occur immediately after the previous deployment is successful, rather than on a schedule
  • 6746 - Tenant Variables are not Versioned
  • 7372 - Fixed an issue where projects could not be converted to version controlled if they relied on an action template referencing a non-existent package
  • 7384 - Disallow JSONP on API endpoints
  • 7377 - Harden-InstallationDirectory.ps1 is now signed
  • 7367 - should never rely on version-controlled processes having relics in the DB. this fix makes sure we get the correct usages from the correct storage

Changes in Octopus Server 2022.2.7580

  • 7690 - Reduced number of ids per request when retrieving resources via /all?ids

Changes in Octopus Server 2022.2.7499

  • 7571 - Improve EventRelatedDocument population

Changes in Octopus Server 2022.2.7462

  • 7681 - Fixed an issue where a Nevermore error would be shown if logging in with OAuth took longer than 30 seconds

Changes in Octopus Server 2022.2.7457

  • 7636 - Improved performance of searching packages from external Maven feeds

Changes in Octopus Server 2022.2.7388

  • 7663 - Fixed an issue where Health Checks for Azure App Service targets failed for clouds other than Azure Public (eg Azure Government)

Changes in Octopus Server 2022.2.7362

  • 7551 - Tenant Tags correctly filter deployment targets on Infrastructure screen (regression)

Changes in Octopus Server 2022.2.7336

  • 7666 - Improved performance of retrieving and deleting artifacts
  • 7658 - Added a retry policy with exponential delay when fetching the message bus sequence number to avoid logging too many messages

Changes in Octopus Server 2022.2.7244

  • 7644 - Improved performance of viewing variable sets

Changes in Octopus Server 2022.2.7180

  • 7652 - Address a performance issue when using step templates in a version controlled deployment process
  • 7642 - Fix slow memory leak in Octopus Server

Changes in Octopus Server 2022.2.6971

  • 7603 - Fixed an issue where Run a Kubernetes Script step would fail if the cluster was not available

Changes in Octopus Server 2022.2.6895

  • 7624 - Scheduled Tasks Logs are intermittently missing from the UI but appear in the shared .\TaskLogs folder
  • 7611 - Change how we scan for task logs so we don't enumerate the whole task logs folder which caused performance issues for instances with a large amount of task logs

Changes in Octopus Server 2022.2.6872

  • 7427 - Fixed an issue where Octopus Server would not start when the license is expired

Changes in Octopus Server 2022.2.6849

  • 7620 - Fix external feed lookup error when using a step template that uses an external feed many times in Git deployment process
  • 7610 - Fix issue where Git projects with step templates are permanently broken after changes are made to referenced data

Changes in Octopus Server 2022.2.6832

  • 7598 - SSH workers will no longer deadlock on parent/child deployments

Changes in Octopus Server 2022.2.6764

  • 7544 - Fixed an issue where the configured Web Request Proxy was not respected in Health Checks for Azure App Service deployment targets

Changes in Octopus Server 2022.2.6729

Breaking Changes
  • 7375 - Empty versions in Octostache syntax now throw an error instead of returning a default value
Other Changes
  • 6664 - Workers now perform retention on their package cache
  • 7585 - Fix NullReferenceException being thrown when creating or viewing releases with a version mask
  • 7582 - Fix Unknown Ref Type error showing in the UI after creating a Runbook on a Git project
  • 7579 - Fix issue where action template view permission was incorrectly required when creating releases for processes that used old versions of action templates
  • 7560 - Fix issue where action template view permission was incorrectly required when creating releases
  • 6774 - Semantic version masks are now correctly evaluated from automatic release creation
  • 7538 - Fixed an issue where creating AD users would always result in a timeout if searching for groups took a long time
  • 7548 - Fixed an issue where orphaned task logs would fail to clean up if a null value exists in OctopusServerInstallationHistory
  • 7600 - Support loading resources and creating releases from commits and tags on Git Projects
  • 7415 - Fixed an issue where collecting machinesbyarchitecture would log a null reference exception
  • 7536 - Fixed an issue where some step templates would incorrectly populate version controlled deployment processes
  • 7456 - Fixed an issue where using the Deploy an Azure App Service step to deploy to a FunctionApp running on a Linux-based AppServicePlan would fail with a Bad Request error
  • 7095 - Fixed an issue where using the Deploy to an Azure App Service step to deploy to multiple App Service targets in parallel would fail due to a file lock
  • 7531 - Fixed inconsistent padding in tenant tag set onboarding page
  • 7076 - "Missing Permission" UI and log warnings for CertificateView and AccountView when viewing Project Variables and Library Variable Sets
  • 7532 - Fixed an issue where task logs with duplicate ids couldn't be cleaned up
  • 7535 - Improve the clarity of the update step template button in version controlled projects
  • 7141 - Octopus now supports OAuth code flow with PKCE when a client secret is specified
  • 7530 - Fixed a bug where the user registration page was unusable because it would always show an error
  • 5831 - Make UI more friendly when editing tenant environments that are no longer in the lifecycles
  • 7035 - Add validation error on deployment settings page - when release versioning from an included package is selected with no package selected
  • 7526 - Active Directory group search is now more resilient to transient errors
  • 7523 - Fixed an issue where packages would be missed when searching in the built-in feed
  • 6249 - Route task links in portal task logs to correct space
  • 7497 - Show detailed Timezone text in portal summary
  • 7516 - Enforce ProjectEdit permissions when editing Git Projects
  • 7446 - Added a note about automatic environments being redundant when a lifecycle phase is set to optional
  • 7490 - Removed related document id check from system integrity check
  • 7419 - LDAP being counted as "non-octopus" authenticator
  • 7482 - Include additional behavioural telemetry for self-hosted instances when opted in
  • 7443 - Fixed an issue where deleting a runbook would result in an error Object reference not set to an instance of an object
  • 7174 - Improve script lock tracking and prevent "task not found" error messages
  • 6526 - Fixed an issue where tenants could not be deleted if a project mapping was removed beforehand
  • 94 - Internal server error (500) when Jira access token is revoked
  • 7469 - Fix code editor full screen behaviour in script console to properly show exit button and scrollbars
  • 7318 - Fixes failing integrity checks related to invalid scoped user role data
  • 7157 - Release page now shows correct start time for deployments
  • 7417 - Octopus Server on Linux will no longer attempt to run HTTP.sys
  • 7444 - Fixed issue with cloud target discovery failing when a manual intervention or email step is in the deployment process
  • 7442 - Fix variable preview page showing 'Variables are not supported in Git' error for Git projects
  • 7364 - Deploy an Azure Resource Manager Template variable Bind for the Account Resource Group doesn't work
  • 7349 - Lock related logs no longer showing in task log
  • 7425 - Fixed an issue where deployment changes were aggregating commits across all releases, but weren't including the commits per release
  • 7036 - Package version now displays correctly on the release details page
  • 7388 - Include process-scoped variables in variable preview
  • 7403 - Removed querying the database for the active transaction count. This fixes an issue where errors would appear in the system log every 30 seconds
  • 7422 - Fixed styling regression for our Code editor component in dark mode
  • 7254 - Parent block in task log marked as done when child is still executing
  • 7306 - Active user sessions can now be revoked
  • 7308 - Session invalidation UI for users
  • 7416 - Fixed an issue where UI styles were undefined causing some screens to misbehave and error
  • 7229 - Lifecycle auto-promotions now occur immediately after the previous deployment is successful, rather than on a schedule
  • 6746 - Tenant Variables are not Versioned
  • 7372 - Fixed an issue where projects could not be converted to version controlled if they relied on an action template referencing a non-existent package
  • 7384 - Disallow JSONP on API endpoints
  • 7377 - Harden-InstallationDirectory.ps1 is now signed
  • 7367 - should never rely on version-controlled processes having relics in the DB. this fix makes sure we get the correct usages from the correct storage

Changes in Octopus Server 2022.1.3072

  • 7690 - Reduced number of ids per request when retrieving resources via /all?ids