j
jyothi B
04/03/2023, 9:46 AMmessage has been deleted
y
Yousaf Nabi (pactflow.io)
04/03/2023, 10:46 AM
the application name should be that of your provider in PactFlow 👍 - the provider may not be created (if no consumer contracts involving the provider have been uploaded)
j
jyothi B
04/04/2023, 4:21 PMmessage has been deleted
jyothi B
04/04/2023, 4:21 PMI tried with the provider one and I still face the same issue
jyothi B
04/04/2023, 4:29 PMmessage has been deleted
jyothi B
04/04/2023, 4:30 PMI am also providing you a screenshot to say that I have both provider and consumer contract from pactflow and it says it is compatible
thankyou 1
y
Yousaf Nabi (pactflow.io)
04/04/2023, 5:04 PM
The SwaggerHub integration will search for the latest on the main branch, or deployed or released consumers.
I can see that there is no branch property on your consumer, and I assume it isn't deployed to an environment and marked as such in PactFlow
Yousaf Nabi (pactflow.io)
04/04/2023, 5:04 PM
Yousaf Nabi (pactflow.io)
04/04/2023, 5:05 PM
Consumer contracts must be using the branches and releases feature - it is not compatible with the use of tags.
The compatibility check uses the following selection criteria:
• The latest version for each consumer's main branch
• Any consumer version that is deployed or released to an environment
In selector terminology, this would be:
•{ "mainBranch": true }
•{ "deployedOrReleased": true }
This means each application (pacticipant) should explicitly set their main branch (e.g.,mainordeveloper) and publish contracts for that branch, as well as using themastercommand.record-deployment
See the documentation on selectors for additional information on how these work.
🙌 1
Yousaf Nabi (pactflow.io)
04/04/2023, 5:05 PM
Your application name is now correctly set in SwaggerHub 👍
🙌 1