- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2022 03:37 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2022 03:34 AM
@jeffs2 you need to specify the pool as 'server' when defining the approval job (see bold below).
-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 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2022 03:34 AM
@jeffs2 you need to specify the pool as 'server' when defining the approval job (see bold below).
-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 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2022 01:26 PM
Thanks 🙂 yes it was not there,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2022 01:26 PM
Issue was due to the Pool missing from the yaml code. Resolved