Change Velocity implementation failing ADO pipeline

jeffs2
Tera Contributor

Hi We are trying to implement change velocity using connection to Azure devops (ADO) to automate change creation, but we are having issues with the pipeline test we are going.  This is a first time setup.

We have added the code into the yaml file (code below) but when we run the pipeline we get an error 

 

"Job Approval: Step references task 'ServiceNow-DevOps-Server-Change-Acceleration' at version '1.36.0' which is not valid for the given job target."

 

We loaded the ADO servicenow extension  

Extension details
This extension allows you to integrate Azure Pipelines with ServiceNow DevOps.
Publisher
ServiceNow
Installed version
1.36.0 (Latest)
 
We added in the code by editing the pipeline and created the task using the "ServiceNow DevOps Server Change Acceleration"
 
But the pipeline fails with "Job Approval: Step references task 'ServiceNow-DevOps-Server-Change-Acceleration' at version '1.36.0' which is not valid for the given job target."
 
Can anyone please give us some ideas of what we have missed or doing wrong ? 
---------------------------------------------- Yaml code ---------------------- 
stageSNOW
  displayNameServicenow

  jobs:
    - jobApproval
      steps
      - taskServiceNow-DevOps-Server-Change-Acceleration@1
        inputs:
                  connectedServiceName'XXXXXXX-service-now-ServiceNow DevOps Service Connection'
                  changeRequestDetails: |
                    {
                      "setCloseCode"false,
                      "attributes": {
                        "requested_by": {
                            "name""test user"
                        },
                        "category""DevOps",
                        "priority""2",
                        "comments""This is a sample pipeline script to be added in your change step",
                        "work_notes""Update this to work_notes",
                        "start_date""2022-01-05 11:59:59",
                        "end_date""2022-01-08 11:59:59"
                     }
                    }
 -------------------end of yaml code ---------------------
1 ACCEPTED SOLUTION

danieldavidson
ServiceNow Employee
ServiceNow Employee

@jeffs2 you need to specify the pool as 'server' when defining the approval job (see bold below).

https://docs.servicenow.com/bundle/tokyo-devops/page/product/devops-config/concept/devops-config-azu...

-stage: ChangeRequest
 jobs:
    -job: 'changerequestjob'
     pool: server
     steps:
        -task: ServiceNow-DevOps-Server-Change-Acceleration
         inputs:
            connectedServiceName: 'MyServiceNowInstance'
            applicationName: 'PaymentDemo'
            snapshotName: 'Production-v23.dpl'

The job should be run on server rather than agent pools because a delay in receiving a change approval can lead to compute cost - unlike build it requires almost no resources so is suitable for a server execution.

 

 Thanks to Cyrille@SN/Joe@SN for pointing me to this 🙂

View solution in original post

3 REPLIES 3

danieldavidson
ServiceNow Employee
ServiceNow Employee

@jeffs2 you need to specify the pool as 'server' when defining the approval job (see bold below).

https://docs.servicenow.com/bundle/tokyo-devops/page/product/devops-config/concept/devops-config-azu...

-stage: ChangeRequest
 jobs:
    -job: 'changerequestjob'
     pool: server
     steps:
        -task: ServiceNow-DevOps-Server-Change-Acceleration
         inputs:
            connectedServiceName: 'MyServiceNowInstance'
            applicationName: 'PaymentDemo'
            snapshotName: 'Production-v23.dpl'

The job should be run on server rather than agent pools because a delay in receiving a change approval can lead to compute cost - unlike build it requires almost no resources so is suitable for a server execution.

 

 Thanks to Cyrille@SN/Joe@SN for pointing me to this 🙂

Thanks 🙂 yes it was not there, 

jeffs2
Tera Contributor

Issue was due to the Pool missing from the yaml code. Resolved