You can confirm the setup of these webhooks via Service Hooks in ADO, as mentioned here.
Pipeline webhooks
The in-app instructions are as below:
To set up the webhook for this pipeline, you need to be an owner or admin for the project.
Go to Project settings for the project in Azure DevOps.
On the Service Hooks tab, click Create subscription.
Select the Web Hooks service type and click Next.
Select the Code pushed trigger type and filter to the correct repository, then click Next.
Set the URL field to the payload URL below.
In the HTTP headers section insert the secret as below.
Leave all other settings as default ([Any]) and click Finish.
Repeat the steps for the Pull request created trigger type.
Repeat the steps for the Pull request updated trigger type. Make sure to leave the Change dropdown as **[Any].**
After completing the above steps, you should see 3 more webhook rows (Code Pushed/Pull request created/Pull request updated).
Important to note: For a single pipeline with X number of CI jobs, you should end up with 6 webhook rows in total - 3 to handle the CI job pooling as below, and 3 for the Pipeline to function as per the screenshot below.
These should be configured as per the instructions above and using the URL/secret provided on your Gearset Pipeline.
We can see above that the pipeline ID matches up with the Gearset Pipeline ID, and includes /pipeline in the URL rather than /continuous-integration-job for the CI job webhooks.
CI job webhooks
As mentioned here, Gearset needs one webhook to run all CI jobs.
These are also built up by 3 individual webhooks for the Code Pushed, Pull Request Created, and Pull Request Updated event types, pointing towards webhooks.gearset.com also, but to the /continuous-integration-job URL instead.
This is how the 3 webhooks should look like in ADO when completing the configuration:
