Hey. I have a question regarding

contract_requiring_verification_published

webhook running on

gitlab

and how to use

${pactbroker.providerVersionNumber}

. I’m using commits to version participants. Gitlab doesn’t have functionality to trigger pipeline against specific commit i.e

${pactbroker.providerVersionNumber}

. If I understand documentation correctly webhook should trigger job for selected

${pactbroker.providerVersionBranch}

and then inside the actual job should checkout

${pactbroker.providerVersionNumber}

and execute tests against it ?

it doesn’t trigger provider branches, no, unless those branches are deployed.

@Matt (pactflow.io / pact-js / pact-go) is it recommended to also use it in combination with

contract_content_changed

for feature branches or provider has to “manually” run the verification? e.g Provider has branches

feat-x,

main

and deployment

test

Consumer changes contract on

feat-x

contract_requiring_verification_published

-> triggers provider on

main

and

test

(if different than main)

contract_content_changed

-> triggers feature ?

no, that’s not how that other webhook event works, neither of them trigger branches. Best to read https://docs.pact.io/pact_broker/webhooks#the-contract-content-changed-event for how they work