DevOps Change Velocity - GitHub Deployment Gates for ServiceNow DevOps Change

[Nived K2]

Hi Team,

I am using ServiceNow DevOps Change Automation custom action on the GitHub workflow to create a change request in ServiceNow. It is creating a change request in the ServiceNow instance to pause and resume the workflow run.

But when I use GitHub Deployment Gate capability to decide on whether a new deployment should proceed or halt, the workflow run is not creating a change request in ServiceNow.

Any suggestion ?

Thank you,

Nived K 

[tonychaffe]

Hey @Nived K2 

I have an example workflow if you'd like to take a look at this: 

servicenow_entraid_approvals/.github/workflows/main_tcazr-test-webapp.yml at main · JTonyC/serviceno...

This uses deployment gates - The key is to ensure the following:

1) A common misconception is that using the servicenow-devops-change@v6.1.0 github action is where the change is raised, which isn't the case when using deployment gates.

In the deployment gate model, you use this action to register a 'deployment-gate'. This should define which job triggers the deployment protection rule defined in the GitHub environment.

2) The step which triggers the GitHub deployment protection rule initiates the callback to retrieve the Change Record payload when the deployment gate was registered. 

At this point, the change is created and the Flows start to trigger for evidence collection and assessment.

3) Also ensure the pipeline is associated to an App in DCV and that the step in that pipeline has change control enabled and is associated to a change model.

In theory, this should get you there. Would like to know where you landed 😉