Devops Change Velocity

Install the DevOps Change Velocity application from the ServiceNow Store.

Add custom fields into your planning tool integration to improve configurability and access business-specific information, which facilitates more informed decision-making.

Create customized lists for your List, Change, Tools, and Administration modules. You can create your own version of an existing list, or a new one.

Additional information on Veracode such as association of orchestration tool from security tool, security scan results, and change policies based on security summary tables.

Additional information on Jenkins.

Connect to your ServiceNow Agile Development 2.0 instance to track your products and the stories, epics, and release versions associated with it.

Add or update DevOps change request attributes using the changeInfo REST API, the Default Change Handler subflow, by passing attributes through the pipeline, Update function, or automated flows.

Create applications using the Classic UI or the Service Catalog.

Create applications using the DevOps Change Workspace and associate pipelines, plans, and repositories to it.

In DevOps Change Velocity, an application collects all the up-to-date data that connected tools send about plans, repositories, and pipelines.

After creating an application, you can associate plans, repositories, pipelines, and artifacts with it.

After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.

Base system table archiving rules ensure that DevOps data stored in the Configuration Management Database (CMDB) are systematically archived and purged.

Connect to your Argo CD instance to automate the deployment of applications from GitHub repositories.

Assign roles and tasks to users and groups so that they can perform the required DevOps tasks.

JFrog Artifactory support for GitHub Actions, Azure DevOps, and GitLab in DevOps Change Velocity enables you to import the artifact data published to JFrog Artifactory for the corresponding pipeline executions. This can then be linked with all the DevOps data collected in DevOps Change Velocity, like Work Items, Commits, Quality Summary, Test Runs, and so on, which helps to trace and identify the root causes.

Associate a business application with a JFrog project in the JFrog tool record to create an AppTrust application in JFrog.

You can associate orchestration tool from the Checkmarx tool record and associate the Checkmarx tool record from the orchestration or pipeline record.

You can associate orchestration tool from the Veracode tool record and associate the Veracode tool record from the orchestration or pipeline record.

For manually created DevOps steps, associate each orchestration task in the Orchestration Tasks related list with a DevOps pipeline step to track the activity of each stage in your Azure pipeline.

Multiple work items for a commit are supported in DevOps for Azure DevOps, Bitbucket, GitHub, and GitLab.

Add test report xmls as attachments to DevOps change requests using the attachment API.

Connect to Jenkins using API token authentication instead of user name and password.

Modify your pipeline to automatically create a DevOps change request.

Connect to your Azure DevOps instance to discover boards, repositories, and pipelines to enable change automation and traceability.

Connect to your Bitbucket instance to track Bitbucket repositories, commits, branches, and pull requests.

Bulk commits are supported with GitLab.

You can use the security conditions that are available in the base system or customize them based on your requirement.

Create change requests even with errors in DevOps data retrieval.

You can use the Jenkins Snippet Generator utility to configure how and when the change state and the corresponding policy conditions must be displayed in the Jenkins pipeline job logs. This enables developers to view the status of the change in the console logs of the pipeline itself.

Connect to your Checkmarx instance that is integrated with your CI/CD pipelines to retrieve security scan results. This helps you determine how vulnerable your code is.

Run commits in DevOps are associated to a task execution.

Change control, artifacts, and packages can be configured in the Azure pipeline for integration with DevOps.

Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.

Run base system or modified scheduled jobs to retry processing errored inbound events. Specify the exceptions or errors to retry events that are in an Error state.

Configure SonarQube or SonarCloud scans on MS Azure DevOps pipelines. Check Azure DevOps pipeline executions for SonarQube scans on every stage of the pipeline's execution and fetch lists and details of scans from any stage to DevOps Change Velocity. Drill down on the Scan Details based on categories.

Configure SonarQube scans on Jenkins pipelines.

Configure webhooks in Bitbucket to send sync notifications to the DevOps Change Velocity application.

Configure webhooks in GitHub to send sync notifications to the DevOps Change Velocity application.

Configure webhooks in your Jira Server or Jira Cloud instance to send sync notifications to the DevOps Change Velocity application.

Connect your custom security tool that is integrated with your CI/CD pipelines to DevOps Change Velocity to retrieve security scan results.

Configure Checkmarx scans on your Azure DevOps, Jenkins, GitHub, GitLab, or Harness pipelines.

Configure Jenkins to send real time notifications for your pipeline executions to DevOps Change Velocity.

Configure security tool for GitLab which is not supported in the base system.

Manually configure webhooks in Azure DevOps and test them.

Configure Veracode scans on your Azure DevOps, Jenkins, GitHub, GitLab, or Harness pipelines.

Configure webhooks for Rally to send sync notifications to the DevOps Change Velocity application.

Configure webhooks from the tool record to send data to DevOps Change Velocity after your tool is connected.

Configure webhooks in Argo CD to send sync notifications to the DevOps Change Velocity application.

Configure webhooks in GitLab manually to send job, push, and issues notifications to the DevOps application.

Configure webhooks manually in Harness to send pipeline notifications to DevOps Change Velocity.

Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account.

Create a tool integration from the DevOps Change Workspace for integrating additional orchestration, planning, and coding tools that are not available by default in the DevOps Change Velocity application.

Connect to Agile Development 2.0 and discover plans from it.

Create an Azure DevOps tool record in DevOps Change Velocity to connect, discover, and import Azure DevOps tool data.

Enable categorizing DevOps change request from DevOps properties. Change requests that are created as part of pipeline execution steps can be created with a category other than DevOps.

Create a DevOps change request and associate existing DevOps data through the Classic UI.

Connect your GitHub instance to discover, configure, and import repositories, plans, and pipelines.

Create an GitLab tool record in DevOps Change Velocity to connect, discover, and import GitLab tool data.

Connect your Jenkins instance to discover and track your pipelines, and import your orchestration tasks for end to end traceability and change automation.

Connect to your Jira Server or Jira Cloud instance from the DevOps Change Workspace to discover available plans and register webhooks to track projects, stories, features, and epics.

Connect to your Sonar instance to retrieve scan results.

Create a Split tool record to connect and discover workspaces, environments, segments, and feature flags from the connected Split tool.

Configure a test tool in DevOps to view unit, functional, and performance test results.

You must create webhooks to send inbound events to DevOps Change Velocity using token based authentication.

For user-created integrations, create a DevOps Workflow Studio subflow to collect and transform data from the tool you are integrating.

Delete the connection and credential aliases that do not label any connection or credential record by running a background script. This helps you in freeing up space in your system.

Use these properties to configure settings in the DevOps Change Velocity application.

Use table cleaners on the inbound events table to purge event data records beyond a specified period. Configure a retention policy with table rotation on the auto-flush form to manage table size growth and archiving data beyond the specified duration.

You can use the Azure Invoke REST API in your YAML or Classic Azure pipeline to configure change control for DevOps.

Azure Boards work items are mapped to default ServiceNow DevOps states and types during import. You can use the DevOpsAzureDevOpsWorkItemHelper script include to customize the mappings.

Cascade record deletion is implemented to delete all dependent lower level DevOps records whenever a parent or higher level DevOps entity is deleted. Confirmation popups ensure that you understand that data will be lost when you delete a record (for example, the record of a tool connection).

Enable the change acceleration feature of DevOps Change Velocity for automatic change request creation in your pipeline, and use change approval flows and policies to automate approval under certain conditions.

Change acceleration is supported in DevOps Change Velocity for GitLab jobs.

The DevOps artifact package and its associated artifact versions are used to determine which commits are included in a DevOps change.

Configure how the closure information, change state, and change request fields are updated from within a pipeline in the change step of the pipeline.

Perform the following steps to integrate your GitHub Apps using the JWT bearer token.

Perform the following steps to integrate your GitHub Apps using Authorization code.

Use the DevOps Insights application with ServiceNow Performance Analytics to gain insight into your DevOps environment.

Learn how ServiceNow DevOps Change Velocity helps your Development and Change Management teams accelerate change and connect their DevOps tool chain with ServiceNow to automate change processes.

Get an overview of how DevOps Change Velocity integrates with your external DevOps toolchain and the tools supported for this integration.

Scope access levels are required when using a personal access token (PAT) to access Azure DevOps during setup.

Use the Pipeline UI to visualize interactions and results across a pipeline execution. This graphical view shows pipeline step progression and other details for each pipeline.

When you use a Jenkinsfile, steps are created, mapped, and associated to orchestration tasks automatically instead of manually.

Software Quality Results display scan details from SonarQube scans configured on your GitHub Actions, Jenkins, Azure DevOps, or Harness pipelines.

Test tool integration lets you view test results in DevOps for Jenkins, Azure DevOps, GitHub, GitHub Enterprise, and GitLab unit, functional, and performance tests.

User-created integrations are for integrating additional planning, coding, and test tools that are not available by default in the DevOps Change Velocity application.

DevOps Change Velocity enables you to use fit-for-purpose change models that allow better flexibility in defining change models or processes to reflect modern development practices.

Send change request numbers to the Jenkins pipeline steps or logs when a change request is created in ServiceNow DevOps.

The DevOps Change Velocity APIs provides endpoints that enable the interaction with external DevOps tools.

Reference information to provide additional details about DevOps Change Velocity such as tables, users, roles, properties, errors, limitations, and others.

View the list of scan checks available in DevOps Change Velocity to get recommendations on fixing any errors that might exist.

Clone the DevOps Change Velocity application from one instance to another.

If any conrefs are broken, re-add them from the doc/source/reuse/domain-separation/domain-separation-overview.dita file. In the short description, edit the first sentence to state whether domain separation is supported or not and add the application name. Keep the conref at the end that describes domain separation.Domain separation is unsupported for DevOps Change Velocity. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

The DevOps Insights dashboard provides a flexible graphical view of operational and business reports. Use the dashboard to evaluate the results of your overall DevOps process.

To help you plan and implement updates to your DevOps processes, DevOps Insights displays a variety of configurable reports that are grouped by type of metric. From the DevOps Change Workspace, select the DevOps Insights icon ( filter icon ) to view the reports.

DevOps Insights properties configure how DevOps Insights workspace data is displayed in reports.

Set log levels in the Jenkins plugin for ServiceNow DevOps based on the extent of log detail you need for debugging.

Connect to your JFrog instance using the DevOps Change Workspace playbook to track artifact repositories published to JFrog.

Connect to an instance of the JFrog artifact tool to enable you to track artifacts published to JFrog.

Connect to your JFrog instance to track artifacts published to JFrog from pipeline executions in Jenkins, GitHub Actions, Azure DevOps, and GitLab.

With ServiceNow DevOps Change Velocity, you can import data from your DevOps tool chain to the ServiceNow platform and deliver changes faster without sacrificing compliance.

DevOps log levels allow you to filter logs by level as well by a particular tool or application. Log levels in the DevOps application let you decide the extent of log detail you need for debugging.

As an alternative to making a connection using the standard setup process, you can use manual configuration mode to set up a webhook manually.

Set up the integration user account to enable integrating with your third-party tools.

Products that use an application model in the CSDM support hierarchies of applications. You can customize hierarchies to simplify tracking of "rolled-up" data on DevOps Insights reports. This is used for the Product filter in insights.

Identify the root cause of errors that occur in DevOps Change Velocity, and see the corresponding steps that might resolve them.

Processing sequence and waiting logic for rerun jobs are different when you reuse or create a change request as part of a rerun job.

Enable the DevOps Custom HTTP Retry Policy for most tool communication from ServiceNow flows to automatically retry failed requests when a step encounters an intermittent issue, such as a network failure or request rate limit.

You can integrate additional security tools that are not supported in the base system in DevOps Change Velocity.

The System Health dashboard lets the DevOps administrator view the overall health of integrations, connectivity status, as well as view trends of inbound event processing data.

Integrate DevOps Change Velocity with any orchestration tool that is not supported in the base system.

Connect to your Azure DevOps instance using the DevOps Change Workspace playbook to collect data for planning, coding, orchestration, artifact, and software quality functions.

Create, connect, discover, and configure your Bitbucket instance using the DevOps Change Velocity workspace.

Create a DevOps change request and associate existing DevOps data through the Workspace UI.

Enable integration with ServiceNow DevOps in Split tool and restrict approvers to only the enabled integration for your environment.

Filter out ignorable DevOps events before they trigger a Flow execution to improve performance.

Retrieve the change request number in a Jenkins pipeline based on specific change details by running the snDevOpsGetChangeNumber script.

Configuration information on GitHub Actions, such as, secrets, workflows, and limitations.

Use the GitHub Deployment Gate capability to decide on whether a new deployment should proceed or halt.

Connect to your GitHub instance to discover repositories, plans, pipeline definitions and configure real-time notifications or polling to enable change traceability and automation.

Enable change tracking for the pipeline in the tool record page in DevOps Change Velocity.

Connect to your GitLab instance to discover plans, repositories, and pipeline definitions and configure real-time notifications or polling to enable change traceability and automation.

GitLab Docker Image supports change creation in GitLab pipelines containing parallel jobs.

GitLab pull (merge) request pipeline executions, which goes through change acceleration before moving to production, can be tracked in DevOps Change Velocity. This integration also collects GitLab merge requests meta data to persist in DevOps Change Velocity. The data is linked with the change created in the merge request pipeline execution and can be used for applying change policies, review, and approval.

Learn about the terms and concepts in DevOps Change Velocity.

Connect to your Harness instance to discover pipeline definitions and configure real-time notifications or polling to enable change traceability and automation.

Reduce instance overhead by skipping step-level pipeline processing for accelerated change management and evidence collection for GitHub Actions, Azure DevOps (ADO), Jenkins and GitLab orchestration tools.

Use the service catalog to onboard a new app and import historical DevOps data for that app. Enable polling to import data that is mapped to associated plans, repositories and pipelines on a scheduled frequency.

DevOps Change Velocity makes it easy to manage artifacts published through Azure DevOps build pipelines. You can import and track these artifacts and manage the packages in DevOps Change Velocity.

Use the DevOps Insights dashboard to evaluate the results of your overall DevOps process. Use the DevOps Pipeline UI view to visually analyze your pipeline executions.

Several types of components are installed with DevOps Change Velocity, including tables, users, roles, and scheduled jobs.

Integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity for end to end change traceability and automation.

Integrate DevOps Change Velocity with JFrog AppTrust applications to automate change request creation, approval, and evidence collection as application versions are promoted through life-cycle stages.

Connect to your Jenkins instance to discover pipeline definitions and configure real-time notifications or polling to enable change traceability and automation.

Configure JFrog plugin for Jenkins to publish, deploy, or download artifacts.

Configure your Azure DevOps instance to enable upload and download of JFrog artifacts.

Pipeline samples for GitHub containing steps to upload and download artifacts for GitHub.

Pipeline samples for GitLab containing steps to upload and download artifacts for GitHub.

Connect to your Jira server or cloud instance to discover plans and enable real-time notifications for projects, issues, and releases.

Manage Jenkins, GitHub Actions, and Azure DevOps (ADO) pipeline’s pull requests for GitHub, Bitbucket, and ADO coding sources 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.

Create Jira, GitHub or Jenkins tool with parent alias set to respective spoke alias instead of DevOps Basic authentication. Use a script include to reset parent alias to spoke alias for existing or onboarded tool.

Model an Azure pipeline by mapping the pipeline to an app, and mapping DevOps Change Velocity pipeline steps to Azure pipeline jobs.

Model a GitLab basic CI pipeline by mapping the pipeline to an app, and mapping DevOps pipeline steps to GitLab pipeline jobs.

Model a Jenkins pipeline by mapping the pipeline to an app, and mapping DevOps pipeline steps to Jenkins stages.

Use nested and parallel stages in scripted Jenkins pipelines to speed up your pipeline execution. Change requests are created for nested and parallel stages and not just for the parent stage.

Notifications are sent to tool users on expiration of tool credentials to alert them. Notifications are also sent proactively before the expiration of tool credentials for GitHub tools created with basic authentication. This enables tool users with the sn_devops.tool_owner or sn_devops.admin roles to update the tool credentials and prevent any loss of data.

Connect to your Agile Development 2.0 instance using the DevOps Change Workspace playbook to enable tracking of stories and epics.

Connect your Argo CD instance using the Classic UI in DevOps Change Velocity.

Connect to your Argo CD instance using the DevOps Change Workspace playbook to automate the deployment of applications from GitHub repositories.

Create, connect, discover, and configure your Azure DevOps instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your Bitbucket instance using the Classic UI.

Connect to your Checkmarx instance to retrieve scan results.

Connect your Checkmarx instance using the ServiceNow Service Catalog.

Connect to your Checkmarx instance using the DevOps Change Workspace playbook.

Connect to your GitLab instance using the DevOps Change Workspace playbook to discover plans, repositories, and pipelines.

Connect to your Harness instance using the DevOps Change Workspace playbook to discover pipelines.

Connect to your Jenkins instance using the DevOps Change Workspace playbook to discover pipelines.

Connect your Jira Server or Jira Cloud instance to discover, configure, and import projects and work items such as stories, epics, and features.

DevOps Change has a pre-build playbook setup for users to configure a new tool. Custom tool integrations can be created using the guided playbook experience in the DevOps Change Workspace.

Use the onboarding catalog items as a self-service approach to onboard your DevOps tools and apps.

Connect to your Veracode instance to retrieve scan results.

Connect your Veracode instance using the ServiceNow Service Catalog.

Connect to your Veracode instance using the DevOps Change Workspace playbook.

After installing DevOps Change Velocity, you can integrate with your DevOps toolchain and automate change requests directly from the DevOps Change Workspace.

Parallel stages in a release pipeline are now processed concurrently and displayed in the DevOps pipeline UI in real time. Base system pre-deployment conditions and release gates enable you to create change requests that include details from parallel stages.

Connect to your GitHub instance using the DevOps Change Workspace playbook to discover, configure, and import repositories, plans, and pipelines.

Connect to your Rally instance using the DevOps Change Workspace playbook to configure webhooks and discover plans.

With this integration, you can configure and expose data like projects, user stories, and defects from the Rally. You can then associate these planning objects to application for end-to-end traceability.

Connect to your Broadcom Rally instance to discover plans and configure real-time notifications to enable change traceability and automation.

In DevOps Change Velocity, when a tool is throttled, processing of new events is delayed until the throttling expires and the tool status changes to Throttled. This is available for Azure DevOps, GitHub, and GitLab.

Enable the Force Tracking Check field in the Jenkins configuration form to create a pipeline tracking file in Jenkins. ServiceNow DevOps makes a REST call to Jenkins to update the tracking file when the Track field in a pipeline is modified.

Disable the prompts recommending the use of DevOps Change Workspace from appearing while creating tools and applications using Classic UI, Service Catalog, Service Portal, and Employee Service Center.

Rerun or redeploy Azure DevOps build, release changes, or pipelines that are failed or canceled in that stage or pipeline. The reattempts display on the DevOps pipeline UI as continuous runs instead of creating new executions.

Retrieve data associated with a change request based on the specified relation type using the DevOpsChangeRelationshipHelper script include.

Run health check scans on your DevOps Change Velocity instance and get recommendations on fixing any errors that might exist.

Create, connect, discover, and configure your Agile Development 2.0 instance using the ServiceNow Service Catalog.

Connect your Sonar instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your Bitbucket instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your GitHub instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your GitLab instance using the ServiceNow Service Catalog.

Connect your Jenkins instance using the ServiceNow Service Catalog to retrieve data like artifacts, test results, scan results, and so on.

Connect your JFrog instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your Jira Server or Jira Cloud instance using the ServiceNow Service Catalog.

Create, connect, discover, and configure your Rally instance using the ServiceNow Service Catalog.

Connect your Sonar instance using the ServiceNow Service Catalog.

Security scan results display scan details from security scans configured on your GitHub Actions, Jenkins, Azure DevOps, GitLab, or Harness pipelines.

Use the ServiceNow custom actions to collect data related to change request creation, Sonar scan, artifact registration, and package registration in your pipeline with the help of the generic Docker Container Image.

View the change request state and the corresponding policy conditions in the Azure DevOps pipeline console logs whenever the state of a change request is updated.

Use the custom actions from the GitHub marketplace to collect scan data, manage workflows, and update change request details.

Create Azure DevOps OAuth 2.0 credential and use them to connect your Azure DevOps instance.

To create a DevOps tool integration, your integration developer configures DevOps tool integration settings, and a Workflow Studio subflow to collect and transform data from the source tool. Then your DevOps admin configures your DevOps tool connections.

Set up OAuth 2.0 Authorization Code credentials for Bitbucket in DevOps Change Velocity to use a more secure authentication method.

Learn about the setup process for DevOps Change Velocity that is required before configuring integrations with your toolchain.

Create OAuth 2.0 credentials for GitHub Apps or OAuth apps and use them to connect your GitHub instance.

Integrate your GitLab account with your ServiceNow instance by creating a custom OAuth application in GitLab and authenticating requests from ServiceNow DevOps.

Authenticate a Rally tool connection using OAuth 2.0 credentials.

Connect to your Sonar instance using the DevOps Change Workspace playbook.

Connect to your SonarQube instance that is integrated with your CI/CD pipelines to retrieve code quality and code security results.

Connect to your Split.io instance to manage feature flags requests directly from you ServiceNow instance.

Add test results to DevOps change requests using the test capability of the DevOps - POST /devops/tool/{capability} API. The API is available for all test types for various tools connected to DevOps Change Velocity.

For tools including GitLab, Rally, Split.io, Jira, Bitbucket, and Argo CD, you have to test webhooks manually if there is any issue with the connection.

Permissions required in your third-party tool to connect to DevOps Change Velocity.

Enable and configure specific pipelines in Azure DevOps that you want to track. Select the pipelines you want to monitor and receive job notifications from Azure DevOps.

Update the change model in your existing pipeline steps using the DevOps Pipeline Migration to Change Models catalog item.

Get and update the change request details associated with an Azure DevOps pipeline.

Update the change request details associated with a Jenkins pipeline by running the snDevOpsUpdateChangeInfo script in the pipeline.

You can perform permission checks and update credentials like passwords and access tokens for your tools from the tool details page.

Send change request rejection or cancellation reason along with approver name and the change request number to Jenkins pipeline logs.

If your tool credential has changed, you must update the credentials in your ServiceNow instance to avoid getting disconnected.

Review the adoption journey of the DevOps Change Velocity application to enable a phased (crawl, walk, run, fly) approach toward complete automation of change approvals.

Customize or recreate the DevOps Change Request Manual Approval, DevOps Change Request Minimal Automation Approval, and DevOps Change Request Advanced Automation Approval flows based on your requirements using a flow or a script.

Artifacts and packages enable DevOps Change Velocity to track development and testing activities across a wide range of deployment and release models. This feature ensures that pipeline activity stored in the DevOps data model can be retrieved and applied when artifacts are created and released at different times or in different pipelines.

Utilize the features of DevOps Change Velocity to efficiently manage your DevOps tools and processes.

Connect to your Veracode instance that is integrated with your CI/CD pipelines to retrieve security scan results. This helps you determine how vulnerable your code is.