Overview
Table of contents
Introduction
Bridge the gap between distributed DevOps/SRE teams and centralized ServiceNow platform owner teams by automatically generating Change Requests. Utilize data from your existing CI/CD tools against sophisticated change policies to accelerate your pipeline.
Dataflow

- Create a Work Item in
Azure Boardsand note the Work Item ID (e.g. AB#14) and assign the item to a developer. - Make your code and configuration changes and commit your changes to
GitHub.
NOTE: Makes sure to set the commit message to the
Work Item IDrelating the code change to theAzure Boardswork item.
- Trigger the
ADO Pipelineto start the build and deployment of your changes. - Service is built and the Docker image is published to
Docker Hubready for final deployment. - The
ADO Pipelinepauses, and a Change Request is automatically generated in ServiceNow for approval. - The
Change Requestis reviewed in ServiceNow and approved after reviewing all the changes. - The
ADO Piplineis released and the Docker image is deployed to theAzure Kubernetesenvironment
Components
| Component | Description |
|---|---|
| Azure DevOps Boards | Microsoft Azure Backlog tracking tool for your distributed teams. |
| GitHub Source Control | Leading Source Code hosting platform for Version Control & Collaboration for your distributed teams. |
| Azure DevOps Pipelines | Microsoft Azure Pipelines used to continuously Build, Test, and Deploy to any Platform and Cloud. |
| Docker Hub | Leading Docker Public Registry for finding and sharing Docker Container Images with your distributed teams. |
| ServiceNow DevOps Change Velocity | ServiceNow Change Automation for your Cloud Native Source code. |
| ServiceNow DevOps Config | ServiceNow Change Automation for your Cloud Native Configurations & Properties. |
| Azure Kubernetes | Microsoft Azure mananaged Kubernetes Cluster for your Cloud Native Workloads. |
Next Steps
- Follow the Guide to implement in your environment.