-
-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verification results are not published to Pact Broker for maven project #538
Comments
It should be automatic if you are loading the pacts from the pact broker. Can you run the verification with debug level logging enabled? |
Yes, I can run the verification in debug mode, and I added the <pact.verifier.publishResults>true</pact.verifier.publishResults> into our configuration block. But the Last Verified value is still not sent to Pact Broker. |
I just helped another person with this problem (but with Gradle), and their issue is they has configured the verifier to load the pact from a URL (to the pact in the broker) instead of configuring it just to query the broker. Check that you have configured a |
Thanks!!! It works. The problem is that we did not put the Our |
You're welcome. But I agree it is confusing. The |
I'm opening this again to track fixing up the confusing configuration tags. |
I clicked the wrong button and closed this question by accident. Anyway thanks! :) Yes. I realised it just now. |
I'm having the same problem. The plugin seems to have no issues finding and verifying pacts but "Last verified" is never updated in the broker. I'm running the mvn pact:verify goal and my pom looks like this:
|
@LucasAndersson you need to run the latest version of the Maven plugin. |
Hi, I updated the pact to version 3.5.5 for our Gradle project, and the verification results are sent back to pact broker successfully. However, it seems that this feature is not working on Maven project.
Do I need to do extra configuration on our project to be able to have the function?
Could you please provide more information in your documentation?
Thanks :)
The text was updated successfully, but these errors were encountered: