---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# ServiceNow DevOps custom actions from GitHub marketplace

# ServiceNow DevOps custom actions from GitHub marketplace {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read  
Use the custom actions from the GitHub marketplace to collect SonarQube scan data, security data, pause or resume workflow, or resume workflow until a change request is approved or rejected in your instance, or get and update change request details
and so on.

Alternatively, you can use Docker container images to implement custom actions for GitHub Actions pipelines. For more information, see [Implement custom actions for pipelines using a generic Docker container image](https://servicenow-prod.fluidtopics.net/lyDd5Y1L9yyAuDzJFwe0tg "Use the ServiceNow custom actions to collect data related to change request creation, Sonar scan, artifact registration, and package registration in your pipeline with the help of the generic Docker Container Image.").

## ServiceNow DevOps SonarQube custom action {#ariaid-title2}

Save the SonarQube scan results of a project initiated by the workflow run in your ServiceNow instance. You must create the SonarQube tool in your instance and use the ServiceNow
DevOps SonarQube custom action at the steps level of a job in the workflow.  
View the SonarQube analysis results using one of the following methods:

* Navigate to DevOpsSoftware Quality ResultsSoftware Quality Summary.
* Navigate to DevOpsOrchestrateTask Execution and selecting a relevant Task Execution record.
{#servicenow-devops-sonarqube-custom-action__ul_a4f_zsv_45b}  
Perform the following tasks to use the custom action.

* Create SonarQube tool in your instance.Generate token from UserMy AccountSecurity page in your SonarQube tool and create tool in the ServiceNow instance using the generated token. For more information, see [Onboard SonarQube to DevOps Change Velocity --- Workspace](https://servicenow-prod.fluidtopics.net/h3bJwqhHuGsIhFYOzm3BFw "Connect to your Sonar instance using the DevOps Change Workspace playbook.") and [Onboard SonarQube to DevOps Change Velocity --- Classic](https://servicenow-prod.fluidtopics.net/4~zfDL~g_S2EwCqbxHR3Aw "Connect to your Sonar instance to retrieve scan results.").

* Create the following Secrets to save SonarQube scan results in the ServiceNow instance.
  * SONAR_HOST_URL: SonarQube instance URL. For example, <kbd class="ph userinput">https://sonarcloud.io</kbd>
  * SONAR_PROJECT_KEY: The key to identify a project in the SonarQube instance. For example, <kbd class="ph userinput">org.examples:demo</kbd>
  {#servicenow-devops-sonarqube-custom-action__ul_cw4_zsb_35b}
* Configure the ServiceNow DevOps SonarQube custom action in the workflow.

  The custom action `servicenow-devops-sonar` must be configured at steps level of job in the workflow with uses keyword. The inputs
  of this custom action must not be tampered to save SonarQube analysis results in the ServiceNow instance. For more information, see [ServiceNow DevOps Sonar](https://github.com/marketplace/actions/servicenow-devops-sonar-scan-results).
{#servicenow-devops-sonarqube-custom-action__ul_vf2_4sb_35b}

## ServiceNow DevOps Test Report custom action {#ariaid-title3}

Save unit test results of the project initiated by the workflow run in your ServiceNow instance. The ServiceNow
DevOps Test Report custom action must be used at the steps level of job in the workflow.

View the unit test results saved in your ServiceNow instance by navigating to DevOpsTest ResultsTest Summaries.

You can also view by navigating to DevOpsOrchestrateTask Execution and clicking a relevant Task Execution record.  
Perform the following tasks to use the custom action.

* Create Secrets in the GitHub Repository.
* Configure the DevOps Test Report custom action in the workflow.

  The custom action `servicenow-devops-test-report` must be configured at steps level of job in the workflow with uses keyword. The
  inputs of this custom action must not be tampered to save the unit test results in your ServiceNow instance. For more information, see [ServiceNow DevOps Test Report](https://github.com/marketplace/actions/servicenow-devops-unit-test-results).
{#servicenow-devops-test-report-custom-action__ul_q5l_txb_35b}

## ServiceNow DevOps Register Artifact custom action {#ariaid-title4}

Save artifacts created or deployed by the workflow run in your ServiceNow instance. Use the ServiceNow
DevOps Register Artifact custom action at steps level of job in the workflow.

View the artifacts details saved in your instance by navigating to DevOpsArtifactArtifacts.  
Perform the following tasks to use the custom action:

* Create Secrets in the GitHub Repository.
* Configure ServiceNow DevOps Register Artifact custom action in the workflow.

  The custom action `servicenow-devops-register-artifact` must be configured at steps level of job in the workflow with uses
  keyword. The inputs of this custom action must not be tampered to save artifact details in your instance. For more information, see [ServiceNow DevOps register artifacts](https://github.com/marketplace/actions/servicenow-devops-register-artifact).
{#servicenow-devops-register-artifact-custom-action__ul_m2m_lyb_35b}

## ServiceNow DevOps Register Package custom action {#ariaid-title5}

Save packages created or deployed by the workflow run in the ServiceNow instance. Use the ServiceNow DevOps Register Package custom action at steps level of job in the workflow.

View the package details saved in the ServiceNow instance by navigating to DevOpsArtifactPackages.  
Perform the following tasks to use the custom action.

* Create Secrets in the GitHub Repository.
* Configure ServiceNow DevOps Register Artifact custom action in the workflow.

  The custom action `servicenow-devops-register-package` must be configured at steps level of job in the workflow with uses
  keyword. The inputs of this custom action must not be tampered to save artifact details in your instance. For more information, see [ServiceNow DevOps register package](https://github.com/marketplace/actions/servicenow-devops-register-package).
{#servicenow-devops-register-package-custom-action__ul_rc2_czb_35b}

## ServiceNow DevOps Change Automation custom action {#ariaid-title6}

Create a change request in the ServiceNow instance to pause and resume the workflow run from the ServiceNow instance.

Use the ServiceNow
DevOps Change Automation custom action at steps level of job in the workflow. If the change is not created within the time period specified in the threshold (changeCreationTimeOut), and the
abortOnChangeCreationFailure parameter is enabled, the pipeline will be aborted.

This custom action creates a change request in ServiceNow, enables the Change Control option, and polls the ServiceNow instance at the defined time interval for change status until either the change is approved or rejected or the timeout threshold (timeout) is reached. GitHub aborts the workflow run if the timeout threshold is reached and the abortOnChangeStepTimeout parameter is enabled.

This custom action immediately resumes the workflow run when change receipt is enabled for pipeline in ServiceNow without waiting for the change to be approved or rejected in the ServiceNow instance.

View the change created for the workflow run in the ServiceNow instance by navigating to DevOpsOrchestratePipeline Change Requests.

The change number with status pending_decision is displayed in the GitHub Actions console while polling the ServiceNow instance for change status. The details like change comments, approved by, approved on, and status are logged in GitHub Actions console after the change is approved or rejected or canceled by the user in the ServiceNow instance.

You can navigate to the console logs in your pipeline to view the state of a change request when a change request is created, change details will be displayed as per the polling time interval. The policy
conditions associated with the change request state will also be evaluated and displayed in the logs. For example, if the DevOps Change Request Advanced Automation policy is activated, the policy conditions will be evaluated and the
corresponding decision made (auto-approve/auto-reject/manual-approval) will be displayed in the logs.  
The following change request details are displayed:

* number
* details
* status
* sys_id
* type
* risk
* priority
* changeState
* plannedStartDate
* plannedEndDate
* changeRequestURL
{#servicenow-devops-change-automation-custom-action__ul_az3_2p1_tcc}

Note:  
changeState is the state of the change request, and status is the status of the step execution.  
The logs for policy conditions will be displayed for the base system change flows as follows:

* DevOps Model Change Policy: Only logs will be displayed on change creation and when the change state is updated.
* DevOps Change Request Minimal Automation Policy: Logs along with change decision and policy conditions corresponding to the change decision will be displayed.
* DevOps Change Request Advanced Automation Policy: Logs along with change decision and policy conditions corresponding to the change decision will be displayed.
{#servicenow-devops-change-automation-custom-action__ul_y3x_1jt_xxb}  
The change policy input and decision conditions are stored in the Decisions \[sys_decision_question\] table. Logs will be displayed if the following fields and operators are used as input for policy conditions:

Fields
:
    * code_coverage
    * commits_without_work_item
    * integration_tests_failed
    * load_tests_failed
    * regression_tests_failed
    * num_of_outages_in_last_7_days
    * num_of_current_outages
    * num_of_open_incidents
    * total_num_of_commits
    * tests_passing_percent
    * risk
    * code_security
    * commits
    {#servicenow-devops-change-automation-custom-action__ul_qkg_xjt_xxb}

Operators
:
    * \<=
    * \>=
    * !=
    * =
    * \<
    * \>
    * ISNOTEMPTY
    * ISEMPTY
    * BETWEEN
    * ANYTHING
    * NSAMEAS
    * SAMEAS
    * GT_FIELD
    * LT_FIELD
{#servicenow-devops-change-automation-custom-action__ul_dst_kpt_xxb}  
Note:  
If any field is modified in a change policy other than the base system fields, then those fields must be manually added to the flow for policy conditions to be evaluated.  
Perform the following tasks to use the custom action.

* Create Secrets in the GitHub Repository.
* Configure ServiceNow DevOps Change Automation custom action in the workflow.

  The custom action `servicenow-devops-change` must be configured at steps level of job in the workflow with uses
  keyword. The inputs of this custom action must not be tampered to create change in your instance and poll for change status every number of seconds. For more information, see [ServiceNow DevOps change automation](https://github.com/marketplace/actions/servicenow-devops-change-automation).
{#servicenow-devops-change-automation-custom-action__ul_klm_51c_35b}

## ServiceNow DevOps Get Change Github Action {#ariaid-title7}

Retrieve the change request number in a GitHub Actions pipeline based on specific change details.

The [ServiceNow DevOps Get Change Github Action](https://github.com/ServiceNow/servicenow-devops-get-change) custom action must be added at the step level in a pipeline job to retrieve the change request number from a ServiceNow instance by specifying change details.

## ServiceNow DevOps Update Change Github Action {#ariaid-title8}

Update change request details associated with a GitHub Actions pipeline.

The [ServiceNow DevOps Update Change Github Action](https://github.com/ServiceNow/servicenow-devops-update-change) custom action must be added at the step level in a pipeline job to update the change request in a ServiceNow instance. The change request number whose details need to
be updated and the change request details to be updated must be specified as input.

## ServiceNow DevOps Security Results Action {#ariaid-title9}

Retrieve security scan results in ServiceNow.

The [ServiceNow DevOps Security Results Action](https://github.com/ServiceNow/servicenow-devops-security-result) custom action must be added at the step level in a pipeline job to retrieve security scan results in ServiceNow.

*[\>]: and then