Consolidated page of all release notes for DevOps Change Velocity from Washington DC to Xanadu.
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 Washington DC to Xanadu.
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 Xanadu
Before you upgrade to Xanadu, review these pre- and post-upgrade tasks and complete the tasks as needed.
| Release |
Release notes |
Washington DC |
No updates for this release. |
Xanadu |
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.
|
New features
Between your current release family and Xanadu, new features were introduced for DevOps Change Velocity.
| Release |
Release notes |
Washington DC |
- GitHub Issues integration
- Discover GitHub issues in GitHub repositories as part of the planning capability to link the GitHub issues with GitHub code commits.
- Implement custom actions for pipelines using generic Docker container image
- Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline using the custom actions for GitLab.
- User-created orchestration tool integration support
- Integrate DevOps Change Velocity with any orchestration tool that is not supported in the base system to discover the orchestration tool, configure webhooks, import historical data, receive live data, and enable change
control on your pipelines.
- GitLab pull request for change approval
- Track GitLab merge request (pull request) pipeline executions in DevOps Change Velocity, link pull request and orchestration pipelines and to enable change approval tracking.
- Jira Cloud integration
- Integrate DevOps Change Velocity with Jira Cloud and track Jira Issues for the configured projects.
- JFrog Artifactory for GitHub, GitLab, and Azure DevOps
- Import the artifact data published to JFrog Artifactory for the corresponding pipeline executions for GitHub Actions, GitLab, and Azure DevOps.
- OAuth 2.0 authentication for Azure DevOps (ADO)
- Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method.
- OAuth 2.0 authentication for Jira Cloud
- Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method.
|
Xanadu |
- Change Management in SOW Admin Center
- Configure Change Management features from the Service Operations Workspace
Admin Center to increase change efficiency, accelerate change approvals, drive data-driven risk analysis, and leverage DevOps data for change automation.
- OAuth 2.0 authentication for Azure DevOps (ADO)
- Use OAuth 2.0 authentication to connect your Azure DevOps tool with DevOps Change Velocity ensuring a more secure authentication method.
- OAuth 2.0 authentication for Jira Cloud
- Use OAuth 2.0 authentication to connect your Jira Cloud tool with DevOps Change Velocity ensuring a more secure authentication method.
- Bitbucket Cloud tool integration with ServiceNow
- Integrate the Bitbucket Cloud coding tool with DevOps Change Velocity to connect, discover, import, and process real-time repository events in DevOps Change Velocity.
- DevOps Change Workspace UI for simplified creation of custom tool integration with planning, coding and orchestration capabilities
- 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.
- Import based evidence collection
- Improve instance efficiency by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions and Azure DevOps (ADO) orchestration tools.
|
Changes
Between your current release family and Xanadu, some changes were made to existing DevOps Change Velocity features.
| Release |
Release notes |
Washington DC |
- Enhanced automated change creation
- Avoid issues that might occur in the automated change request creation guided procedure because of the tool connection state.
- New state transition flows for DevOps change model
- Move and track changes through added transition flows for the Change - DevOps - New and Change - DevOps - Schedule states in the DevOps change model.
- Error handling for DevOps flows
- View errors corresponding to a change request in the work notes of a change request and console logs of the pipeline tool when a business rule or data policy causes an issue while updating a change in the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, or DevOps Change Request Advanced Automation Approval flows.
- DevOpsChangeRelationshipHelper script to retrieve change data
- Retrieve data associated with a change request based on the specified relation type using the DevOpsChangeRelationshipHelper script include.
- New property to specify retry limit
- Specify the maximum number of times the discover action will be automatically retried after it reaches the rate limit using the Maximum limit for the number of times the discover action that exceeds the rate limit
will be retried property.
- Import request restart
- Restart an import request from the Import Request record that couldn’t be completed due to an error.
- Automatically associate repositories
- Repositories are automatically associated to applications when a corresponding pipeline identifies commits of repositories that are not yet associated.
- Unit test type support for GitHub
- Automatically publish unit test results of types NUnit, pytest, jest, JUnit, and XUnit from GitHub Actions workflows without any custom Application Programming Interface (API) calls.
- Change request creation with errors in DevOps data retrieval
- Enable change request creation even if there is an error in retrieving the DevOps data in a pipeline.
- Multiple ServiceNow DevOps configurations in the same Jenkins instance
- Configure multiple ServiceNow DevOps connections in one Jenkins server.
- Custom actions for GitLab using Docker
- Retrieve and update change request details associated with a GitLab pipeline and publish unit test results. Automatically update close code based on the overall pipeline execution status for simple GitLab pipelines.
- Manual retry of downstream events
- If an error occurs for an event, and there are subsequent downstream events associated with it, then you must manually retry each downstream event by selecting the Retry button. Automatically retrying
of downstream events is not supported anymore.
- Enhancements to DevOps Model change
-
- In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process.
- To make the Change - DevOps – Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created.
- The new Change – DevOps – Update execution state flow in the DevOps model means you no longer have to activate the DevOps Change Request Manual Approval flow to send a callback to the third-party orchestration tool.
- Fast-track your change process by using a new DevOps Simplified change model, which doesn’t contain the Assess state. Change approval for this model is based on the DevOps Simplified Model Change policy.
- Branch details for artifacts and packages
- Branch details from pipeline executions are now available for artifacts and packages for better tracking.
- Create lists
- Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change
Workspace.
- Jira Server connection using API key
- Connect to your Jira Server using API key authentication rather than basic authentication.
- GitHub Actions reruns
- Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.
- Generalized Docker Container solution to support any orchestration tool
- Use the generalized and extensible Docker Container solution to integrate any orchestration tool with DevOps Change Velocity for invoking pipeline actions like change request creation and collecting relevant DevOps data without having to rely on tool specific plugins or extensions.
- Simplified onboarding of planning tools that are not supported in the base system
- Integrate planning tools that are not supported in the base system by leveraging transformer rules. GitLab Issues is now available as one of the planning tools and is built leveraging this new approach so you can discover plans, import work items, and configure webhooks for work items (issues) in GitLab.
- Default BitBucket branch property
- Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property.
|
Xanadu |
- Reflow for configurable workspace
- DevOps Change Configurable workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. For more information, see
the Accessibility information section that follows.
- DevOps data in change request
- View, add, and edit DevOps data in a manually created change request in Service Operations Workspace for a unified change request experience in both DevOps Change Workspace and Service Operations Workspace.
- Enhancements to DevOps Model change
-
- In-product guidance enables you to leverage DevOps models and easily create DevOps changes without disruption of your change process.
- To make the Change - DevOps – Implement flow of the DevOps model more suitable for DevOps changes, change tasks are no longer automatically created.
- The new Change – DevOps – Update execution state flow in the DevOps model means you no longer have to activate the DevOps Change Request Manual Approval flow to send a callback to the third-party orchestration tool.
- Fast-track your change process by using a new DevOps Simplified change model, which doesn’t contain the Assess state. Change approval for this model is based on the DevOps Simplified Model Change policy.
- Branch details for artifacts and packages
- Branch details from pipeline executions are now available for artifacts and packages for better tracking.
- Create lists
- Option to create customized lists added to the Changes, Tools, and Administration modules in the DevOps Change
Workspace.
- Jira Server connection using API key
- Connect to your Jira Server using API key authentication rather than basic authentication.
- GitHub Actions reruns
- Re-running failed GitHub jobs will now use the existing change request created for the failed jobs instead of creating new change requests.
- Generalized Docker Container solution to support any orchestration tool
- Use the generalized and extensible Docker Container solution to integrate any orchestration tool with DevOps Change Velocity for invoking pipeline actions like change request creation and collecting relevant DevOps data without having to rely on tool specific plugins or extensions.
- Simplified onboarding of planning tools that are not supported in the base system
- Integrate planning tools that are not supported in the base system by leveraging transformer rules. GitLab Issues is now available as one of the planning tools and is built leveraging this new approach so you can discover plans, import work items, and configure webhooks for work items (issues) in GitLab.
- Enhanced manual DevOps change creation experience
- Add work items data in a manually created DevOps change request in Service Operations Workspace for ITSM.
- Default BitBucket branch property
- Specify the default Bitbucket branch name that must be used to create an import request in the sn_devops.bitbucket_default_branch property.
- Additional scans for DevOps Health Scan Content pack
- 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 Bitbucket Data Center
- Import pull-request records for Bitbucket Server or Data Center for improved insights and efficiency.
- Change request creation with errors in DevOps data retrieval for Harness pipelines
- Enable change request creation even if there is an error in retrieving the DevOps data for a Harness pipeline.
- Branch name filter
- 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.
- Test summary name in GitHub Actions
- The servicenow-devops-test-report custom action in GitHub now includes an optional test-summary-name parameter to specify the test summary results name.
- Token based authentication for Rally
- Configure webhooks for Rally using token based authentication instead of using the integration username and password.
- Renamed variables for Docker
- 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
- Security scan results on the change record associated to a pipeline execution with a linked package are now displayed in the Security Summaries tab.
- Source of commits in SOW
- 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.
- Track file changes
- The Track file changes option is now disabled by default when a repository is configured to prevent any potential security risks.
- Close code value for a change request
- 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.
- Support for MID Server cluster
- 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.
- Improved UX for DevOps Change health scans
- Run health scans and analyze findings efficiently in the DevOps Change workspace with an intuitive and user-friendly interface.
- Pipeline association for GitHub Actions
- 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.
- Tool connection check status
- 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.
|
Removed
Between your current release family and Xanadu, some DevOps Change Velocity features or functionality were removed.
| Release |
Release notes |
Washington DC |
No updates for this release. |
Xanadu |
No updates for this release. |
Deprecations
Between your current release family and Xanadu, some DevOps Change Velocity features or functionality were deprecated.
| Release |
Release notes |
Washington DC |
No updates for this release. |
Xanadu |
No updates for this release. |
Activation information
Review information on how to activate DevOps Change Velocity.
| Release |
Release notes |
Washington DC |
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.
|
Xanadu |
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.
|
Additional requirements
If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.
| Release |
Release notes |
Washington DC |
No updates for this release. |
Xanadu |
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 |
Washington DC |
No updates for this release. |
Xanadu |
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 |
Washington DC |
No updates for this release. |
Xanadu |
- Accessibility improvements
- Accessibility improvements were completed to create a configurable workspace that supports WCAG 2.1 Level AA conformance.
- Reflow
-
The Configurable Workspace supports reflow, which enables pages and content to be zoomed up to 400% through your browser settings without loss of content or functionality. Additionally, content can be enlarged
without scrolling in two dimensions at a width equivalent to 320 CSS pixels or a height equivalent to 256 CSS pixels. Page layouts are transformed into a vertical, stacked view automatically when users increase browser zoom to
400%.
-
This enhancement helps users with low vision or who have trouble seeing web content in a browser due to monitor size, device type, poor lighting, or other situations. Reflow can be turned off
with a system property for instances, experiences, and pages. See Reflow for Configurable Workspace for details.
|
Localization information
If there are specific localization considerations for DevOps Change Velocity we have noted them here.
| Release |
Release notes |
Washington DC |
No updates for this release. |
Xanadu |
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 |
Washington DC |
- Discover GitHub issues in GitHub repositories as part of the planning capability.
- Collect data related to change request creation, Sonar scan, artifact registration, and package registration in your GitLab pipeline.
- Retrieve data associated with a change request using the DevOpsChangeRelationshipHelper script.
See DevOps Change Velocity for more information.
|
Xanadu |
- Leverage DevOps data for change automation by configuring Change Management features from the Service Operations Workspace
Admin Center.
- Benefit from accessibility improvements to create a configurable workspace that supports Web Content Accessibility Guidelines (WCAG) 2.1 Level AA conformance.
See DevOps Change Velocity for more information.
|