Hi!! I have a scenario where inn the application w...
# general
p
Hi!! I have a scenario where inn the application where we are trying to figure out the configuration to publish pact (in consumer CI) and run provider verification and publish its results (in provider CI). I am using pact-cli for publishing pacts to the pact-broker from consumer app and pact-ref-verifier docker image for running and publishing provider verification to the oss pact-broker. I am confused as to how the below scenario should look like: 1. If I publish the pacts in my consumer application using --branch
develop
after a PR is merged, then how is
{ "mainBranch": true }
in consumer version selector configuration in my provider picking only this branch’s pacts and not the others ? Asking since my consumer has older release branches where a PR merge can happen and there i would be publishing pacts with --branch
release-someversion
or should i rather use
"matchingBranch": true
since all my applications (provider or consumer) are named the same way
m
Is develop the main branch for that app? If so, that's why
👍 1
You can check by hitting the pacticipant API endpoint and checking (there is probably a CLI command to check also but I'm on mobile)