Combined DevOps Change Velocity release notes for upgrades from Yokohama to Zurich
Summarize
Summary of Combined DevOps Change Velocity release notes for upgrades from Yokohama to Zurich
This consolidated release notes page provides ServiceNow customers with essential information for upgrading DevOps Change Velocity from the Yokohama release to Zurich. It covers important upgrade tasks, new features, changes, deprecated features, and activation instructions to help ensure a smooth transition and to leverage the latest capabilities.
Show less
Important Upgrade Considerations
- Customers upgrading from Yokohama must run the ReConfigure Bitbucket Server Repositories for PullRequest scheduled job to enable import of pull request records from Bitbucket Server or Data Center.
- New customers or those using zBoot instances who want to create type-based workflow change requests must set the
com.snc.changemanagement.changemodel.typecompatibilitysystem property to True.
New Features Introduced Between Yokohama and Zurich
- Harness Integration: Discover Harness pipelines and configure real-time notifications for change traceability and automation.
- DevOps Health Instance Scan: Run or schedule health scans to detect anomalies and issues in your DevOps Change Velocity instance.
- Bitbucket Cloud Integration: Connect and process real-time repository events from Bitbucket Cloud.
- DevOps Change Workspace UI: Simplified UI to create custom tool integrations across planning, coding, and orchestration capabilities with embedded documentation and self-service support.
- Import-Based Evidence Collection: Accelerate change management by skipping step-level pipeline processing for GitHub Actions, Azure DevOps, GitLab, and Jenkins.
Key Changes and Enhancements
- Simplified onboarding of unsupported orchestration tools using a generic integration framework.
- Added custom fields support in planning tool integrations for better configurability and decision-making.
- Enhanced DevOps Health Scan content with proactive checks for upgrade-related issues, plugin/version incompatibilities, and failing pipelines.
- Improved handling of change request creation when errors occur retrieving data from Harness pipelines.
- New capabilities such as branch name filters for build number searches, token-based authentication for Rally webhooks, and security scan result displays on change records.
- Support for MID Server clusters to improve load balancing and failover protection during tool connections.
- Enhanced user experience for DevOps Change health scans with an intuitive interface.
- Improved pipeline governance in GitLab by showing change request details directly in the GitLab console.
- Automatic update of tool connection status from Disconnected to Connected following successful system-generated checks, while preserving manual disconnects.
- New roles added for vulnerability integration with Veracode and other plugins, assigned to DevOps Tool Owner roles.
- Upgraded Node.js version for the ServiceNow DevOps extension in Azure DevOps to version 20.x.
Removed and Deprecated Features
No features or functionalities were removed or deprecated between Yokohama and Zurich releases.
Activation and Installation
DevOps Change Velocity must be activated or installed via the ServiceNow Store. Customers should submit requests through the store to access the latest version and cumulative release notes.
Additional Notes
- There are no new browser requirements, localization updates, or accessibility changes introduced in the Zurich release.
- Highlighted improvements include integration with Harness for pipeline discovery and automation, health scan anomaly detection, import-based evidence collection efficiency gains, and MID Server cluster support for tool connections.
This information equips ServiceNow customers to effectively prepare for and execute upgrades to the Zurich release of DevOps Change Velocity, enabling improved automation, health monitoring, integration flexibility, and operational efficiency.
Consolidated page of all release notes for DevOps Change Velocity from Yokohama to Zurich.
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 Zurich.
Important information for upgrading DevOps Change Velocity to Zurich
Before you upgrade to Zurich, review these pre- and post-upgrade tasks and complete the tasks as needed.
| Release | Release notes |
|---|---|
Yokohama |
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 the com.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 to search for this job and run it. |
Zurich |
No updates for this release. |
New features
Between your current release family and Zurich, new features were introduced for DevOps Change Velocity.
| Release | Release notes |
|---|---|
Yokohama |
|
Zurich |
|
Changes
Between your current release family and Zurich, some changes were made to existing DevOps Change Velocity features.
| Release | Release notes |
|---|---|
Yokohama |
|
Zurich |
|
Removed
Between your current release family and Zurich, some DevOps Change Velocity features or functionality were removed.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Deprecations
Between your current release family and Zurich, some DevOps Change Velocity features or functionality were deprecated.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Activation information
Review information on how to activate DevOps Change Velocity.
| Release | Release notes |
|---|---|
Yokohama |
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. |
Zurich |
Install DevOps Change Velocity by requesting it from the ServiceNow Store. |
Additional requirements
If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Browser requirements
If any specific browser requirements were introduced or changed for DevOps Change Velocity we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Accessibility information
Review details on accessibility information for DevOps Change Velocity, such as specific requirements or compliance levels.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
Localization information
If there are specific localization considerations for DevOps Change Velocity we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
No updates for this release. |
Zurich |
No updates for this release. |
Highlight information
If there are specific highlight considerations for DevOps Change Velocity we have noted them here.
| Release | Release notes |
|---|---|
Yokohama |
See DevOps Change Velocity for more information. |
Zurich |
See DevOps Change Velocity for more information. |