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 2021.3.12928 to 2022.3.1591

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

Octopus 2021.3

Highlights

Built-in support for Amazon's Elastic Container Service (ECS) will make your ECS deployments easier. Our opinionated UI step guides you through the setup and builds the CloudFormation template, so you don't have to write configuration files or custom scripts.

This release includes some other noteworthy updates:

  • We delivered a new TypeScript API client for Octopus Deploy.
  • The Config as Code early access preview (EAP) is available to all customers.
  • Try our new Visual Studio Code extension that supports the Octopus Configuration Language (OCL) for Config as Code.
  • The Terraform Provider for Octopus Deploy supports script modules, tenant variables, and Worker Pools.
  • We improved our Go API client and TeamCity plugin for Octopus Deploy.
  • Octopus Cloud supports Azure AD, Google, and Okta as authentication providers, alongside Octopus ID.

Read our blog post to learn more.

Breaking changes

This release includes 3 breaking changes.

New default behavior for GET machines/{id}/tasks

We added runbook run activity to the deployment target screen. In support of this change, GET machines/{id}/tasks now returns both deployments and runbook runs. You can specify a type parameter to filter the results: Deployment or RunbookRun.

Learn more about this change in the GitHub issue.

Recommended version of Mono to run Calamari

Calamari can execute on the Mono framework. We recommend 5.14.0 as the minimum version of Mono for running Calamari.

Learn more about this change in our SSH target requirements documentation.

Recommended version of the Octopus .NET API client

We recommend 11.3.3453 as the minimum version of the Octopus .NET API client for interacting with Octopus Server 2021.3.

Customers who use the Octopus .NET API client to work with teams, roles, and permissions must use version 11.3.3453 of the client (or newer) to ensure compatibility with Octopus Server 2021.3.7491 and newer.

Learn more about this change in the GitHub issue.

Release notes

These are the features and fixes you'll get by upgrading from 2021.3.12928 to 2022.3.1591.

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

  • 7577 - Bugfix for SQL error thrown when creating tenant deployment with a ProjectView permission scoped to 100's of projects

Changes in Octopus Server 2022.1.2735

  • 7534 - File and git cache cleanup no longer runs under the task cap

Changes in Octopus Server 2022.1.2733

  • 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

Changes in Octopus Server 2022.1.2679

  • 7553 - Fixed the Full Table Cache to update stale data when rolling back a transaction

Changes in Octopus Server 2022.1.2669

  • 7435 - Sql timeout deleting from DeploymentRelatedMachine - RelatedDocumentStore.PopulateDeploymentRelatedMachines

Changes in Octopus Server 2022.1.2661

  • 7521 - Prevent deleting a channel when it would also delete a step used as the versioning rule
  • 7154 - Fixed duplicated variable when importing projects with import/export

Changes in Octopus Server 2022.1.2637

  • 7538 - Fixed an issue where creating AD users would always result in a timeout if searching for groups took a long time

Changes in Octopus Server 2022.1.2584

  • 7542 - Improve handling of missing local branches when fetching changes from git remotes in config-as-code projects
  • 7323 - URL escaping percentage sign in branch name

Changes in Octopus Server 2022.1.2556

  • 7518 - Improve performance of apply retention policies task
  • 7522 - Fixed issue with missing tenant variables showing for projects or environments not linked

Changes in Octopus Server 2022.1.2495

  • 7519 - Fixed an issue where all requests were blocked if the dynamic extensions configuration was set to null

Changes in Octopus Server 2022.1.2488

  • 7514 - Fix feed error when a step template was used multiple times in the same process for Git projects
  • 7515 - Fix error in Git projects when using a step template with a package parameter

Changes in Octopus Server 2022.1.2474

  • 7516 - Enforce ProjectEdit permissions when editing Git Projects

Changes in Octopus Server 2022.1.2438

  • 7501 - Trust the SQL Server certificate by default

Changes in Octopus Server 2022.1.2412

  • 7496 - Improve tenant missing variable performance

Changes in Octopus Server 2022.1.2386

  • 7412 - The Create or Edit release page will now show a warning icon next to packages which could not be resolved from their feed

Changes in Octopus Server 2022.1.2364

  • 7486 - Fixed an issue where switching to a branch with a / character in the name would cause the portal to redirect the user to the default branch
  • 7477 - Fixed scheduled deployments creating phantom server tasks and releases

Changes in Octopus Server 2022.1.2342

  • 7475 - Project data is refreshed only when deployment process is saved successfully

Changes in Octopus Server 2022.1.2332

  • 7453 - Fix some step package input values not correctly serialising to OCL
  • 7471 - Audit login succeeded and failed events for authentication providers
  • 7467 - Fix missing request body error when downloading system report
  • 7462 - Step using Nuget feed no longer functions correctly after conversion to version controlled project

Changes in Octopus Server 2022.1.2300

  • 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

Changes in Octopus Server 2022.1.2278

  • 7071 - Release versioning will only be updated when the step associated is updated, and better validation to prevent versioning package step changes to the referenced package
  • 7448 - Sync the deployment settings in portal once deployment process is saved successfully

Changes in Octopus Server 2022.1.2274

  • 6179 - Task Logs - Parent project now receives Success With Warning status from child project

Changes in Octopus Server 2022.1.2264

  • 7457 - Fix Runbook step template updates throwing a not found error
  • 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.2232

  • 7451 - Fix task logs not being deleted when a deployment or runbook run is deleted
  • 7466 - Viewing Step Templates in Library produces an error

Changes in Octopus Server 2022.1.2133

  • 7281 - Active Directory authentication will now correctly login users when forms authentication and Sign in with a domain options are used

Changes in Octopus Server 2022.1.2128

  • 7444 - Fixed issue with cloud target discovery failing when a manual intervention or email step is in the deployment process

Changes in Octopus Server 2022.1.2121

Breaking Changes
  • 7376 - Config as Code API urls renamed
  • 7342 - Share git credentials between config as code projects
Other Changes
  • 7381 - Validator for creating and modifying runbooks are now consistent
  • 7411 - Block converting a project to Git until ARC settings have been manually cleared. Some users were missing the warning message and were not aware the ARC is not supported for Git projects
  • 7343 - Bugfix - If a project failed to convert to a git project, and git filesystem cleanup then executed, the repository would fail to re-attempt conversion until a server restart
  • 7407 - Fix Object reference not set to an instance of an object. error sometimes appearing on Project Version Control settings page
  • 7394 - Swagger now loads correctly
  • 7406 - Bugfix: Allow deleting channels for git projects
  • 7402 - Bugfix: Loading DeploymentTemplate for release created prior to project getting converted to vcs may throw 404
  • 7369 - Fixed an issue with Jira integration blocking release creation when integrating with Jira Server
  • 7380 - Fix "early access feature" wording on the Configure Version Control dialog
  • 7374 - The /api/users/{id}/spaces endpoint has been updated such that it wont cause thread starvation or deadlocks
  • 7018 - The same docker image is no longer acquired multiple times
  • 7429 - Config as Code feature moved out of EAP and into General Availability
  • 7371 - Fixed an issue where Structured Configuration Variables were not correctly applying to XML files
  • 7305 - User session timeouts can now be configured when using username and password authentication
  • 71 - Include Tenant name in Jira Environment DisplayName
  • 6439 - Unable to clear the project logo
  • 7363 - Bugfix for react error when editing YAML directly on K8S Deployment step
  • 7151 - Fix issue where TinyType exception would be thrown when converting a project to version control
  • 7356 - Fixed GetRunbookSnapshotVariables and GetReleaseVariables endpoints
  • 7347 - Spaces endpoint doesn't honour the name query parameter
  • 6994 - Deploy a Release step in a runbook doesn't allow selection of the same project
  • 7314 - Fixed an issue where attempting to save an ECS Cluster Deployment Target without setting the AWS Account field would not give an understandable validation message
  • 7300 - Sample paths in Git File Storage Location UI don't appear to be correct
  • 7309 - Fixed a bug where selecting an API key expiration could cause the page to error

Changes in Octopus Server 2021.3.12928

  • 7578 - Fixed an issue where release retention would fail if more than 2100 projects exist