-
I have a generic account/user setup in CI system (Jenkins) for the webhooks to trigger provider verification builds whenever a new pact is published (event - contract_requiring_verification_published)…
-
The consumer version selectors currently support a `fallbackBranch` option, which is useful because you can first check to see if the consumer has a matching branch name, and if not fall back to the d…
-
Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:
```
{ "deployedOrReleased": true }
{ "deployed": true }
{ "releas…
-
Reference: https://docs.pact.io/pact_broker/advanced_topics/pending_pacts
"Pending pacts" is a feature for providers, to avoid new consumer expectations breaking the tests and blocking their pipeli…
-
We tried setting the :pact.verifier.publishResults this way `lein with-profile pact pact-verify :pact.verifier.publishResults="true" :pact.provider.version="provider-version"` but it isn't publishing…
-
Hi Team,
We're trying to write pact provider tests in Clojure using pact jvm.
In kotlin we have an option to publish the results to broker using `System.setProperty("pact.verifier.publishResults"…
-
As you guys can see:
Verifying a pact between Consumer and Provider
[from Pact Broker http://localhost:82/pacts/provider/Provider/consumer/Consumer/version/abc (Tag tag-ultima)]
The download …
-
Waiting for api job trigger support from circleci: https://discuss.circleci.com/t/api-job-trigger-fails-on-2-1-circle-project/27010
-
# Pre issue-raising checklist
I have already (please mark the applicable with an `x`):
* [x] Upgraded to the latest Pact Broker OR
* [ ] Checked the CHANGELOG to see if the issue I am about to …
-
These are a bit out of date, and don't show the difference between "verifying a single pact at a URL" (used for webhook flow) and "verifying all the pacts for a provider" (normal provider CI).
http…