Combined DevOps Change Velocity release notes for upgrades from Yokohama to Australia
On this page
Combined DevOps Change Velocity release notes for upgrades from Yokohama to Australia
Consolidated page of all release notes for DevOps Change Velocity from Yokohama to Australia.
How to use this page
To help you prepare for your upgrade, we have combined the cross-family DevOps Change Velocity release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Australia.
Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says “No updates for this release.”
Important information for upgrading DevOps Change Velocity to Australia
Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
-
Upgrade information
If you are a new customer or are using a zBoot instance and you want to create type-based workflow change requests in DevOps Change Velocity, you must add thecom.snc.change_management.change_model.type_compatibility property and set it to True. For more information, see Add a system property.
If you are an upgrading customer, you must run the ReConfigure Bitbucket Server Repositories for PullRequest job to re-configure your existing Bitbucket Server or Bitbucket Data Center repositories so that pull request records can be imported. You can navigate to All > System Definition > Scheduled Jobs to search for this job and run it.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## New features
Between your current release family and Australia, new features were introduced for DevOps Change Velocity.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
Integrate the Bitbucket Cloud coding tool with DevOps Change Velocity to connect, discover, import, and process real-time repository events in DevOps Change Velocity.
Integrate a new custom tool across planning, coding and orchestration capabilities with basic know-how of ServiceNow using an intuitive DevOps Change Workspace UI. It offers easy navigation to the ServiceNow Platform for defining transformer or adapter rules, or integrate the ability to do so within the Workspace wherever applicable, and embeds necessary documentation links and tooltips to support self-service.
Discover Harness pipelines and configure real-time notifications to enable change traceability and automation by integrating the Harness orchestration tool with DevOps Change Velocity.
Detect anomalies and issues in the instance by running or scheduling health scans on your DevOps Change Velocity instance.
Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), GitLab and Jenkins orchestration tools.
</td></tr><tr><td>
Zurich
</td><td>
Authenticate a Rally tool connection using OAuth 2.0 credentials to strengthen your tool security.
Connect to GitHub Enterprise Server with data residency controls to keep your organization’s code and data in your preferred geographic location.
Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), GitLab and Jenkins orchestration tools.
</td></tr><tr><td>
Australia
</td><td>
Authenticate a Rally tool connection using OAuth 2.0 credentials to strengthen your tool security.
Connect to GitHub Enterprise Server with data residency controls to keep your organization’s code and data in your preferred geographic location.
</td></tr></tbody> </table>## Changes
Between your current release family and Australia, some changes were made to existing DevOps Change Velocity features.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
Identify any callback processing issues in your instance.
-
Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
-
Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
-
Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
-
-
Auto close without Change Management - State Model [Legacy] plugin
Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.
Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy.
Set the sn_devops.change_request.auto_close_allow_override_start_time ** and sn_devops.change_request.auto_close_allow_override_end_time ** properties as false to consider the change request start and end time instead of the pipeline’s when the autoCloseChange parameter is enabled in a pipeline.
The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.
View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
-
-
Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
-
Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check.
-
Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
-
Verify if any scheduled job has been configured to run as an invalid or non-admin user.
-
Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget.
-
Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
-
Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check.
-
Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
-
Verify if any scheduled job has been configured to run as an invalid or non-admin user.
-
Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget.
-
Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
-
New roles for vulnerability integration
-
The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
-
The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
-
The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
-
The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
-
Additional set of proactive checks focused on problems that tend to occur before or after an upgrade along with identifying configuration issues like plugin and version incompatibilities, or pipelines that chronically fail, have been added.
Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.
Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
Search for build numbers by the branch name while associating DevOps data to a change request in the Service Operations Workspace (SOW) or Classic UI.
The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
Configure webhooks for Rally using token based authentication instead of using the integration username and password.
The environmental variables in the Generic Docker actions for DevOps Change Velocity have been renamed by removing the CI prefix for better clarity.
Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
View the source of commits like pipeline execution, branch, repository, and so on for a change request in the DevOps data section of the Service Operations Workspace.
The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
Two new properties have been added in DevOps Change Velocity, so that you can specify a close code value for a change request based on the change request completion state when the autoCloseChange parameter is enabled.
Integrate orchestration tools that aren’t supported in the base system by leveraging a generic framework.
Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.
</td></tr><tr><td>
Zurich
</td><td>
Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account.
Connect to Bitbucket Cloud using Basic Auth by providing the email address and API token with the required scopes for your Bitbucket Cloud account as app password has been deprecated by Bitbucket.
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
Identify any callback processing issues in your instance.
-
Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
-
Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
-
Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
-
-
Auto close without Change Management - State Model [Legacy] plugin
Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.
Update the sn_devops.commit_rel_change_step_type property to have other step types, like Test or Deploy, use the same commit logic as Prod Deploy.
Set the sn_devops.change_request.auto_close_allow_override_start_time ** and sn_devops.change_request.auto_close_allow_override_end_time ** properties as false to consider the change request start and end time instead of the pipeline’s when the autoCloseChange parameter is enabled in a pipeline.
The node version of the ServiceNow DevOps extension has been upgraded to version 20.x in Azure DevOps.
View change request details like status, sys_id, priority in the GitLab console when a change request is created in GitLab using Docker image.
-
-
Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
-
Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check.
-
Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
-
Verify if any scheduled job has been configured to run as an invalid or non-admin user.
-
Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget.
-
Identify outdated or prolonged discover and import requests using the DevOps -Stale or Long-Running Discover and Import Requests health check.
-
Verify whether webhooks have been configured correctly for any tracked repository, pipeline, or plan in GitHub, GitLab, Azure DevOps, and Jenkins using the DevOps webhook configuration analysis health check.
-
Identify OAuth app configuration issues for GitHub tools in the connected state using the DevOps webhook configuration analysis health check.
-
Verify if any scheduled job has been configured to run as an invalid or non-admin user.
-
Navigate to the Findings list from the DevOps Change Workspace home page by selecting **View all findings ** in the Health scan findings widget.
-
-
Coral theme
Coral is now the default theme for new portal, web, and mobile experiences with Next Experience or Core UI enabled. This theme provides a fresh look and feel, featuring brand-neutral illustrations to enhance your user experience. A dark theme option is available for web and mobile experiences.
Improve load balancing and failover protection by selecting a MID Server cluster when connecting to a tool instance associated with a MID Server cluster. This configuration enables multiple MID Servers with relevant capabilities to be grouped.
Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
When onboarding GitHub Actions pipelines through the App onboarding catalog or the onboarding APIs, now only the selected pipelines are associated with the DevOps app. If no pipeline is selected, all pipelines within the specified repository are associated.
If a tool is marked as Disconnected because of a system-generated failure during an unsuccessful connection check, any subsequent successful check automatically updates the connection status to Connected. If you manually disconnect the tool, the tool status remains Disconnected even if there’s a subsequent successful connection check.
-
New roles for vulnerability integration
-
The sn_vul.app_sec_manager role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the DevOps Vulnerability Integrations plugin (sn_devops_vul_ints) is installed.
-
The sn_vul_veracode.configure_integration role is added to the DevOps Tool Owner [sn_devops.tool_owner] role when the Vulnerability Response Integration with Veracode plugin (sn_vul_veracode) is installed.
-
</td></tr><tr><td>
Australia
</td><td>
Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account.
Connect to Bitbucket Cloud using Basic Auth by providing the email address and API token with the required scopes for your Bitbucket Cloud account as app password has been deprecated by Bitbucket.
Gather JFrog evidence seamlessly and create change records automatically using the improved JFrog integration with DevOps Change Velocity.
Connect to JFrog using the secure bearer token authentication to comply with JFrog’s updated security policies.
Connect to DevOps Change Velocity through HTTP proxy settings using environment variables in your Docker deployment for instances that run a proxy server.
-
-
Identify any callback processing issues in your instance.
-
Identify any access control rule (ACL) that is incorrectly associated with a role in your instance.
-
Verify whether all DevOps tables are present in your instance and confirm whether all metadata in sys_* tables is present.
-
Verify whether all DevOps roles in your instance contain all expected roles, including inherited roles.
-
-
Auto close without Change Management - State Model [Legacy] plugin
Change requests can now be auto-closed without requiring you to install the Change Management - State Model [Legacy] plugin.
</td></tr></tbody> </table>## Removed
Between your current release family and Australia, some DevOps Change Velocity features or functionality were removed.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Deprecations
Between your current release family and Australia, some DevOps Change Velocity features or functionality were deprecated.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Activation information
Review information on how to activate DevOps Change Velocity.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
-
Activation information
Activate DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Important: DevOps Change Velocity is available in the ServiceNow Store. For details, see the “Activation information” section of these release notes.
</td></tr><tr><td>
Zurich
</td><td>
-
Activation information
Install DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Important: DevOps Change Velocity is available in the ServiceNow Store. For details, see the “Activation information” section of these release notes.
</td></tr><tr><td>
Australia
</td><td>
-
Activation information
Install DevOps Change Velocity by requesting it from the ServiceNow Store. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Important: DevOps Change Velocity is available in the ServiceNow Store. For details, see the “Activation information” section of these release notes.
</td></tr></tbody> </table>## Additional requirements
If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Browser requirements
If any specific browser requirements were introduced or changed for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Accessibility information
Review details on accessibility information for DevOps Change Velocity, such as specific requirements or compliance levels.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
-
Accessibility information
-
Dark theme
-
The new Coral theme includes a dark theme option for web and mobile experiences. This option is commonly used to alleviate eye strain and improve readability.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Localization information
If there are specific localization considerations for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
No updates for this release.
</td></tr><tr><td>
Zurich
</td><td>
No updates for this release.
</td></tr><tr><td>
Australia
</td><td>
No updates for this release.
</td></tr></tbody> </table>## Highlight information
If there are specific highlight considerations for DevOps Change Velocity we have noted them here.
<table class=“custom-rows”><thead><tr><th class=“filter”>
Release
</th><th>
Release notes
</th></tr></thead><tbody><tr><td>
Yokohama
</td><td>
-
Integrate with the Harness orchestration tool to discover Harness pipelines and enable change automation.
-
Detect anomalies and issues in your DevOps Change Velocity instance using health scans.
See DevOps Change Velocity for more information.
</td></tr><tr><td>
Zurich
</td><td>
-
Improve visibility into your DevOps data in a single system.
-
Automate the change workflow and approval decisions to increase change velocity while ensuring governance and control.
-
Track the progress of your work items, commits, artifacts, builds, and releases using the change requests to lend additional transparency and provide a single source of truth to all the personas involved.
See DevOps Change Velocity for more information.
</td></tr><tr><td>
Australia
</td><td>
-
Improve visibility into your DevOps data in a single system.
-
Automate the change workflow and approval decisions to increase change velocity while ensuring governance and control.
-
Track the progress of your work items, commits, artifacts, builds, and releases using the change requests to lend additional transparency and provide a single source of truth to all the personas involved.
See DevOps Change Velocity for more information.
</td></tr></tbody> </table>Parent Topic:Products combined by family
Keep exploring.
Find another answer, or bring this documentation into your own tools.