Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions
-
- UpdatedJan 30, 2025
- 8 minutes to read
- Yokohama
- DevOps
Use the ServiceNow DevOps extension for Azure DevOps and Azure DevOps custom actions
Install and configure DevOps extension for Azure DevOps to send build and release notifications from your Azure pipeline to DevOps Change Velocity.
Before you begin
Role required: sn_devops.admin
About this task
You can use ServiceNow DevOps extension on Visual Studio Marketplace - Extensions for Azure DevOps to integrate your Azure pipeline with the ServiceNow DevOps application. For more information about artifacts and packages in DevOps Change Velocity, see Artifacts and packages.
- ServiceNow DevOps service connection
Required to connect the Azure pipeline to ServiceNow
- ServiceNow DevOps Release Gate
Required to enable change control in Azure release (CD) pipelines (in pre-deployment conditions only).
- Agentless (server) job
- ServiceNow DevOps Server Artifact Registration custom task
Required for agentless (server) jobs to register an artifact in the ServiceNow instance
- ServiceNow DevOps Server Package Registration custom task
Required for agentless (server) jobs to register a package in the ServiceNow instance
- ServiceNow DevOps Server Change Acceleration custom task
Required for agentless (server) jobs to automatically create a change request in ServiceNow Change Management as part of the Azure pipeline.
Note: The ServiceNow DevOps Server Change Acceleration task does not require ServiceNow DevOps Server Job Notification tasks. - ServiceNow DevOps Server Get Change custom task
Required to retrieve the change request number in a pipeline based on specific change details for a server job.
- ServiceNow DevOps Server Update Change custom task
Required to update the change request details associated with a pipeline for a server job.
- ServiceNow DevOps Server Artifact Registration custom task
- Agent job
- ServiceNow DevOps Agent Artifact Registration custom task
Required for agent jobs to register an artifact in the ServiceNow instance
- ServiceNow DevOps Agent Package Registration custom task
Required for agent jobs to register a package in the ServiceNow instance
- ServiceNow DevOps Agent Get Change custom task
Required to retrieve the change request number in a pipeline based on specific change details for an agent job.
- ServiceNow DevOps Agent Update Change custom task
Required to update the change request details associated with a pipeline for an agent job.
Note: The ServiceNow DevOps Agent Artifact Registration and ServiceNow DevOps Agent Package Registration tasks are not supported for Release pipelines. - ServiceNow DevOps Agent Artifact Registration custom task
- Software Quality scans (SonarQube/SonarCloud)
- ServiceNow DevOps Build Sonar Registration custom task (for Build pipelines)
- ServiceNow DevOps Release Sonar Registration custom task (for Release pipelines)
Note: The ServiceNow DevOps Build Sonar Registration task is not supported for Release pipelines. - Security scans:
- ServiceNow DevOps Build Security Results custom task (for Build pipelines)
- ServiceNow DevOps Release Security Results custom task (for Release pipelines)
Note: The ServiceNow DevOps Build Security Result task is not supported for Release pipelines.
Procedure
Example


Set up an Azure build (CI) pipeline in DevOps
Use the ServiceNow DevOps extension for Azure DevOps to configure change control and artifacts and packages in your Azure build (CI) pipeline.
Before you begin
Role required: sn_devops.admin
Procedure
Example



Set up an Azure release (CD) pipeline in DevOps
Use the ServiceNow DevOps extension for Azure DevOps to configure change control, and artifacts and packages in your Azure release (CD) pipeline.
Before you begin
Role required: sn_devops.admin
About this task
Phases in an Azure release pipeline are mapped to a step. The step name for a multi-config or multi-agent job must include the phase name only, and not the actual job name derived at pipeline execution run time.
Task executions for skipped jobs are marked as failed.
Procedure
Example

