-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Tags are not published with the Gradle plugin when using providerTags #1423
Comments
Released 4.1.26 with the fix |
I just tried this with 4.1.26 and still could not get a tag published using |
@uglyog I don't think this is specifically related to Gradle. I also have this same problem with maven using version 4.1.28. Unfortunately, this is the latest version I can use due to my project being a java 8 project. Other projects within my company that are using the latest version do not have this issue, but like I say given I have to use a Java 8 supported version the issue persists. |
yeah, the issue doesn't appear to be gradle specific. I am using pact jvm 4.2.14. Tried publishing provider tag with PendingPacts enabled but no luck.
As a work around I was able to add tags through |
This issue is due to: The The |
Thanks for the clarification @uglyog. So, the |
I'm just stating the reason for the current behaviour, but it is not ideal and needs to be fixed. |
According to the documentation you can publish tags when verifying a contract via
providerTags
. I've found that specifyingproviderTags
in thepact
Gradle task does not workWhen I run
./gradlew pactVerify -i -PdevDB -Ppact.verifier.publishResults=true -d
the request withproviderTags
is null and the pact verification result is not tagged in the pact-broker:When I run
./gradlew pactVerify -i -Ppact.verifier.publishResults=true -Dpact.provider.tag=foo -PdevDB -d
, I see the following entry in the gradle output and the pact verification result is tagged in the pact-broker:The project I'm using is configured with the following:
The text was updated successfully, but these errors were encountered: