Combined DevOps Change Velocity release notes for upgrades from Vancouver to Washington DC

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 Vancouver to Washington DC.

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 Washington DC

Before you upgrade to Washington DC, review these pre- and post-upgrade tasks and complete the tasks as needed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.

New features

Between your current release family and Washington DC, new features were introduced for DevOps Change Velocity.


Release	Release notes
Vancouver	Veracode integration with DevOps Change Velocity Connect the Veracode security tool that is integrated with your CI/CD pipelines with DevOps Change Velocity to retrieve security scan results, which help you determine the vulnerability in your code. Checkmarx integration with DevOps Change Velocity Connect Checkmarx that is integrated with your CI/CD pipelines to DevOps Change Velocity to retrieve security scan results, which help you determine the vulnerability in your code. 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 GitLab and GitHub Actions pipelines using 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. 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.
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.

Changes

Between your current release family and Washington DC, some changes were made to existing DevOps Change Velocity features.


Release	Release notes
Vancouver	DevOps change models Use change models in DevOps Change Velocity that enables better flexibility in defining change models or processes to reflect modern development practices. Secure token authentication for integration user Configure Azure DevOps, Jenkins, and GitHub Actions using token-based authentication for the integration user for better security. ServiceNow DevOps change request state in Azure DevOps pipeline logs View the change request state and the corresponding policy conditions in the Azure DevOps (ADO) pipeline console logs whenever the state of a change request is updated without having to navigate to ServiceNow® DevOps Change Velocity. Get and update change request details Retrieve and update change request details associated with an Azure DevOps pipeline and the GitHub Actions workflow by using the ServiceNow® DevOps extensions available in the Azure DevOps and GitHub Actions marketplace. Configure webhooks manually As a tool owner or DevOps admin, access the token and sys_id for webhooks by configuring webhooks manually in your third-party tool rather than configuring them automatically from ServiceNow® DevOps Change Velocity. GitHub Actions deployment gates Enforce quality gates on every deployment environment in GitHub Actions and retrieve the change details from within the Deployment Protection Rule console logs of GitHub Actions. Simplified setup Spend less time in the initial setup of ServiceNow® DevOps Change Velocity thanks to the removal of the CreateDevOpsTool connection setup activity. Validate ServiceNow DevOps extension in Azure DevOps Validate the installation of ServiceNow DevOps extension in Azure DevOps with a playbook activity. Configure webhooks automatically in Rally Configure webhooks automatically as part of the playbook while connecting to the Rally tool. Assign services to the pipeline steps While associating pipelines with an application, for each selected pipeline, all steps or stages are imported from the last successful execution. Update change model in pipeline Update the change model in your existing pipeline steps using the DevOps Pipeline Migration to Change Models catalog item. Manage ADO pull requests Manage Azure DevOps (ADO) pipeline's pull requests for ADO coding source from ServiceNow DevOps. You can enable the change approval process on your pull request to control pull request merge approvals from ServiceNow DevOps and monitor pull request details associated with the change request. New test types supported for ADO Automatically publish ADO test results of test tools reports like NUnit, pytest, jest, JUnit, and XUnit without any custom API calls. GitHub OAuth JWT setup through playbook Configure the GitHub tool using OAuth JSON Web Token (JWT) credentials through the tool onboarding playbook. GitHub Organization support Configure and discover GitHub repositories under an organization. Automatic updation of close code based on pipeline execution status Change created from a pipeline is now automatically closed and updated with the closure notes, actual start and end time, based on the overall pipeline completion status. Guided change automation experience Use better in-product guidance on the various ways to leverage DevOps changes and easily adopt the changes without complete disruption of your change process. Renamed DevOps flows The DevOps Model Change Approval and DevOps Default Change Approval flows have been renamed to DevOps Change Request Manual Approval and DevOps Change Request Advanced Automation Approval flows respectively. Getting started guide Use the Getting started guide from the DevOps Workspace Homepage to get started with DevOps Change Velocity after installation. Create applications using playbook Use the App playbook to create DevOps applications, associate plans, repositories, and pipelines, and import historical data. Configure Jenkins automatically Configure the Jenkins tool automatically directly from within DevOps Change Velocity. 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. 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. 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.
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.

Removed

Between your current release family and Washington DC, some DevOps Change Velocity features or functionality were removed.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.

Deprecations

Between your current release family and Washington DC, some DevOps Change Velocity features or functionality were deprecated.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	No updates for this release.

Activation information

Review information on how to activate DevOps Change Velocity.


Release	Release notes
Vancouver	Install DevOps Change Velocity by requesting it from the ServiceNow Store.
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.

Additional requirements

If any additional requirements were introduced or changed for DevOps Change Velocity we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	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
Vancouver	No updates for this release.
Washington DC	No updates for this release.

Localization information

If there are specific localization considerations for DevOps Change Velocity we have noted them here.


Release	Release notes
Vancouver	No updates for this release.
Washington DC	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
Vancouver	Integrate with the Veracode security tool to retrieve security scan results. Use change models that enable better flexibility in defining change models. Configure Azure DevOps, Jenkins, and GitHub Actions using token-based authentication. See DevOps Change Velocity for more information.
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.