Two Ways to Integrate ServiceNow into Azure DevOps Release Pipeline
Question
Your company has a project in Azure DevOps for a new web application.
The company uses ServiceNow for change management.
You need to ensure that a change request is processed before any components can be deployed to the production environment.
What are two ways to integrate ServiceNow into the Azure DevOps release pipeline? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.BD
An example of a release pipeline that can be modeled through a release pipeline in shown below:
In this example, a release of a website is created by collecting specific versions of two builds (artifacts), each from a different build pipeline. The release is first deployed to a Dev stage and then forked to two QA stages in parallel. If the deployment succeeds in both the QA stages, the release is deployed to Prod ring 1 and then to Prod ring 2. Each production ring represents multiple instances of the same website deployed at various locations around the globe.
https://docs.microsoft.com/en-us/azure/devops/pipelines/releaseTo ensure that a change request is processed before any components can be deployed to the production environment, you can integrate ServiceNow with Azure DevOps by using pre or post deployment gates or deployment control.
A pre-deployment gate is a customizable workflow gate that blocks the deployment process until specific conditions are met. This condition could be ServiceNow change request approval in this case. The pre-deployment gate is defined before the deployment to the Prod stage.
A post-deployment gate is a gate that runs after the deployment to the QA stage. This gate ensures that ServiceNow change request is approved before the deployment to the Prod stage. If the change request is not approved, the deployment to the Prod stage is blocked.
A deployment control is a reusable workflow task that can be added to a release pipeline. The control is added to a stage and is responsible for executing an action. To integrate ServiceNow with Azure DevOps using a deployment control, you need to define a deployment control that invokes the ServiceNow REST or SOAP API. This deployment control can be used to retrieve information about the change request or to update the status of the change request.
Option A and C are the options that define a deployment control that invokes the ServiceNow API, but A is using the REST API and C is using the SOAP API. Option B and D are the options that define pre and post deployment gates, respectively.
So, the correct answers are:
- Define a deployment control that invokes the ServiceNow REST API. (Option A)
- Define a pre-deployment gate before the deployment to the Prod stage. (Option B)
