https://pact.io logo
Join Slack
Powered by
Starting a new thread because I messed the last on...
# pact-jvm
r
Starting a new thread because I messed the last one up. Pact broker retrieves the wrong provider version - meaning it retrieves not the latest version. Here is my issue: The consumer, which pushed-pacts, got verified by a provider with version 
1.0.0
. The provider has made some application changes and performed a 
record-deployment
with version 
1.0.1
. The consumer has also made some changes, pushed-pacts, and triggered a provider verification pipeline. The provider verification pipeline has finished successfully, but no indication of verification results are present in the broker, unless I hard-code the previous provider version (
1.0.0
- not latest) in the verification pipeline, that was used to verify the previous consumer version and retrigger the verification process - then the pact broker does receive the results. When I set the log level to DEBUG, I am can see the pact broker client's logs only if I use version 
1.0.0
! When I use 
1.0.1
I don't see any pact broker client logs🤯 I am using pact-broker version 
2.105.0
. Other then 
record-deployment
, is there any other action I should be taking in order to update a provider's contract version? Thanks
I think I might of misunderstood the usage of 
record-deployment
, and the docs explains only when to perform the action (should be called at the very end of the deployment process), but does not mention why, meaning - in which cases should I 
record-deployment
. Any explanation regarding that would be great.
y
The Pact Broker needs to know which versions of each application are in each environment so it can return the correct pacts for verification and determine whether a pacticular application version is safe to deploy.
• 
record-deployment
is used to model the real life scenario where a deployment causes the previous version of an application to be replaced by a new version. It is used for APIs and consumer applications that are deployed to known instances. When called, it automatically marks the previously deployed version as undeployed.
> The provider verification pipeline has finished successfully, but no indication of verification results are present in the broker, unless I hard-code the previous provider version (
1.0.0
- not latest) in the verification pipeline, that was used to verify the previous consumer version and retrigger the verification process - then the pact broker does receive the results. Without knowing the details on your verification setup, it’s hard to determine. > The provider has made some application changes and performed a 
record-deployment
with version 
1.0.1
. Did the provider run a verification task, verifying consumer contracts against 1.0.1 prior to calling can-i-deploy and subsequently record-deployment. I would recommend running through the ci/cd workshop to get a handle on how a real world scenario plays out
r
Apparently your 
<http://au.com|au.com>.dius.pact.consumer
lib clashed with 
provider
lib and caused the verification tests to not run. I appreciate your help, thanks.
Open in Slack
PreviousNext
Powered by