Skip to main content

Conclusion

We have demonstrated how the CI/CD pipelines of the consumer and provider work with Pact and PactFlow, and how to introduce and release new features using consumer driven contracts, while keeping each project deployable throughout the process.

Principles to remember:

  • Tag application versions with the name of the git branch and ideally associate application versions with the name of the git branch as per the Branches documentation
  • Record the deployment in PactFlow after a successful deployment.
  • Configure the provider to verify the latest pact for the main branch of development, and the currently deployed (or released) versions.
  • Enable "pending pacts" in the provider to ensure that changed pacts don't break provider builds unncessarily.
  • Enable "work in progress pacts" in the provider to automatically verify any pending "feature pacts" during CI verification (allows verification results for feature pacts to be published from CI without having to manually update the provider configuration for each feature pact).
  • Make changes to pacts on feature branches for the consumer, and merge once the feature pact has been successfully verified.