2

I have a consumer that generated the first version of the Pact contract and it uploaded it to the broker. The producer verified that the contract and the verification were published to the broker.

Now I want to extend the contract. When I publish the updated contract to the broker and subsequently run the verification on the producer side, it fails since the contract-fulfilling API is not implemented yet. I'd like to update the contract first, publish it, and avoid breaking the producer build (i.e. not modifying the consumer and the producer in lockstep).

How can I version consumer/producer/contract so I can specify in the producer that it is currently compatible with a specific consumer/contract version?

I'm using Pact JVM/Java (version 3) with Maven. There is no project versioning in pom.xml - it's just 1.0.0-SNAPSHOT version. projectVersion, as configured in the Pact Maven plugin is the same as Maven project version - 1.0.0-SNAPSHOT.

Should I play with projectVersion and tags? Should I upgrade to Pact version 4 and use consumer version selectors?

mgryszko
  • 556
  • 4
  • 12

1 Answers1

0

So I think you're asking about how do effectively add Pact tests into your CI/CD pipeline and feature development workflow?

  1. Effective pact setup guide
  2. CI/CD workshop

The first document explains the general approach, and (2) is a workshop you can follow to implement the steps (in JS). The principles are the same no matter what language you use (in your case Java).

Specifically, however, you will definitely need to use tags to prevent new feature tags from breaking your providers main build (e.g. featureA created by a consumer, won't break the provider that only looks for production and development for example).

You may also want to look at pending pacts (see https://docs.pact.io/pending and the https://docs.pact.io/implementation_guides/jvm/provider/junit5/#pending-pact-support-version-410-and-later) which is a newer feature that prevents new contracts from breaking a provider.

Versioning

So you'll need to add more specific versions to your code to make effective use of Pact (and the workflows provided by the broker). You can specify this with the pact.provider.version system property (e.g. System.setProperty("pact.provider.version", "some git sha");)

We recommend using your revision control SHA in the version.

Matthew Fellows
  • 3,669
  • 1
  • 15
  • 18
  • My company already has an installed broker; we are just exploring the versioning and workflows. Adding Git SHA1 to Pact Maven configuration (through [buildnumber-maven-plugin](https://www.mojohaus.org/buildnumber-maven-plugin/)) + tagging solved my problems – mgryszko Oct 13 '20 at 06:09
  • Nice to hear, hope it goes well, and do join slack.pact.io to chat with the community! – Matthew Fellows Oct 14 '20 at 11:41