pact_broker | Enables your consumer driven contracts | REST library

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.