FAQ for DevOps Change Velocity

[gregholevas]

Frequently Asked Questions - DevOps Change Velocity

 

What are DevOps integrations?

The DevOps Change Velocity application provides an integration framework which enables integration with CI/CD tools like Microsoft Azure DevOps, Jenkins, GitHub Actions, and GitLab along with tools that connect to the pipeline like Jira (for planning) or Veracode (for security scanning). These integrations enable organizations to bridge the gap between development and operations, enabling DevOps teams to roll out releases rapidly and efficiently.

How to integrate with a third-party DevOps tool?

You can integrate your orchestration, planning, coding, artifact, software quality, and security tools with DevOps Change Velocity. Use the DevOps Change workspace for a guided experience, with playbook steps for each activity like connecting, configuring or discovering. You must onboard a minimum of one planning, one coding, and one orchestration tool to enable change outcomes.

What is a DevOps app and how is it useful?

An application is needed to group plans, repositories, and pipelines together which enable tracking automatically and provide associations for DevOps data such as commits linked to work items. You must create an application to enable traceability for user stories, commits, test results, and more. Associating plans, repositories, and pipelines to an application also enables pipeline modeling, change governance, and metric reporting.

How do I automate my change request creation?

You can automate change request creation using a guided procedure in the DevOps Change workspace where you’ll select the pipeline for which you want to automate change, specify change attributes, and modify the pipeline to enable change control. Automated change request creation is then triggered from a pipeline step.

How do I automate my change approval process?

DevOps Change Velocity uses flows and DevOps data (such as work items, commits, code coverage, code security, risk, and test results) to update the state of a change request and automatically approve it based on change approval policies. Three flows are available in the base system that you can clone, customize, and activate (in Flow Designer).