In the business sector, implementing systemic change is not so easy. We should prepare deployment, recovery and testing plans and it should go to the CAB for approval and we should provide a rationale from our end. Before that, every business has its own process for creating changes and it varies according to the type of change. The ticket exchange process is the best way, but it takes more time to process the change. Is it possible to automate the generation of change tickets, instant approval or automatic approvals according to the DevOps process? If so, how to enable it in ServiceNow?If you create a step called Plan, Build, Test, Preprod, production steps, is ServiceNow change ticket automation enabled before moving the production?.

To answer all questions - "ServiceNow DevOps Change Velocity" is the best fit for automatic change ticket generation to manage DevOps Change Lifecycle.

The following are prerequisites required for using the solution. This is an example of Azure DevOps pipeline change ticket automation. Similarly, you should create a prerequisite check for Jenkins, GitHub tools, etc.,

1. Create an ADO service account in ServiceNow2. Collect data from ADO Access with appropriate permissions3. Create a DevOps Resolver Group4. Set the Project/Organization URL in ServiceNow5. Collect the ADO Access Token6. Install the ServiceNow DevOps Extension to ADO via the Visual Marketplace Portal7. Create a Service Connection from ADO and send information to ServiceNow8. Connect a project: Select Workspaces > DevOps Change Workspace.9. Configure webhooks for live data (if you configure webhooks on your Azure DevOps instance and it sends data to the DevOps change rate) Select plans, repositories and pipelines to track and import historical data

10. Install Mid Server (if required)

The following links support enabling integration with ServiceNow and Azure DevOps.

https://docs.servicenow.com/bundle/washingtondc-devops/page/product/enterprise-dev-ops/concept/devop...

Public ADO url to understand and review

https://dev.azure.com/prathyushkondapalli/CorpSite%20M

We must understand that this is a joint venture between ServiceNow and AzureDevOps.1. ServiceNow technician completes items with DevOps Change Velocity Workspace.

2. An Azure DevOps technician completes the items with the '.YAML' file and settings.

I just prepared the high-level architecture how it supports in the business. I have added the Testing Tool called 'Sonar Qube' and it will be added into the ADO Pipeline configuration.

Challenges:1. ADO support provides a project management role to enable integration. This is hindered by organizational constraints. It should explain this to companies and get approval. Get ServiceNow intervention if needed.2. ServiceNow Domain Separation - DevOps user account default user map with parent domain

3. Payload configuration in ADO - Once OOB fields are matched to change ticket automation, this is easy to do, but populating a custom field using an ADO directive is challengeable.

Hope you like it. If any questions or remarks, let me know!

If this helped you in any way, I would appreciate it if you hit bookmark or mark it as helpful.

Regards,

Suresh.