Tim Vahlbrock
01/23/2025, 2:19 PMThomas Kanne
01/28/2025, 2:22 PMcontract_requiring_verification_published
in the Pact-Broker's webhooks as I am working on multiple environments (main branch, integration, stage, prod). I am using Gitlab trigger tokens which trigger a pipeline only running the pactVerify
job (which is a Gradle talk of my project executing the Java PactProviderTest).
As Gitlab only accepts branches and tags as reference (ref
), I don't know how I can pass the right revision to the ref
as my pactbroker.providerVersionNumber
returns a combination of my Gradle project version + the respective Git short SHA (e.g. 1.0.0-a6d33b7a). My tags in Gitlab are named in format v1.0.0. I was thinking about parsing the version and do string manipulation to reach my desired format, but this seems not be possible within a webhook. Alternatively I thought about setting the providerVersionsTags
and use them to pass to the ref
. But this seems to be a complex (and probably dirty) workaround which I am not even sure about if it would work as expected.
Do you have any idea?Hernan Mateika
01/30/2025, 1:53 PMDominic Plourde
01/30/2025, 4:26 PMDimitris Dranidis
01/31/2025, 10:42 AMproduction
. I did not find anything in the pact-broker CLI or in the Pact-broker API. Is there a way?Paul Beigang
01/31/2025, 12:52 PMVictor Vargas
02/05/2025, 8:01 AMMatt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Paul Beigang
02/05/2025, 12:26 PMTim Vahlbrock
02/06/2025, 10:07 AMcontract_requiring_verification_published
event when no provider has ever verified a contract from this consumer? So if I want to trigger the pipeline for a brand new interface I also need to add the contract_content_changed
event to the webhook configuration?Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
Tim Vahlbrock
02/06/2025, 10:47 AMTim Vahlbrock
02/06/2025, 10:48 AMTim Vahlbrock
02/06/2025, 11:06 AMGabriel Vasconcelos
02/07/2025, 11:01 AMPiyush Sardana
02/08/2025, 10:35 AMSpencer
02/11/2025, 3:34 PMGitHub
02/13/2025, 12:30 PMGitHub
03/04/2025, 1:21 PMGitHub
03/06/2025, 5:06 PMGitHub
03/06/2025, 7:01 PMChris
03/11/2025, 6:11 AMpact-broker record-release
?
Also, how do we bulk record-support-ended
them?Ksawery Karwacki
03/17/2025, 5:48 PMGustavo Souza
04/03/2025, 6:16 PMJun Yi
04/10/2025, 3:03 AMstaging
and production
, which may contain different code as features are tested in staging before being rolled out to production.
1. Would it make sense to maintain separate sets of Pact stages for each branch?
2. I've observed that when a webhook is triggered, the verification always runs against the main branch (staging), regardless of which branch initiated the process. This could potentially cause issues when the branches diverge.
Any suggestions on how we can improve this setup or handle branch-specific verification more effectively?
Thanks!Matt (pactflow.io / pact-js / pact-go)
Would it make sense to maintain separate sets of Pact stages for each branch?I’m not sure I entirely follow. The concept of “branches” are there to map changes for a given branch. Are you using
pact-broker record-deployment
when you deploy to each environment?
I’ve observed that when a webhook is triggered, the verification always runs against the main branch (staging), regardless of which branch initiated the process. This could potentially cause issues when the branches diverge.When a webhook fires, it specifies in the payload which version (and branch/environment) that it needs to check against. Your webhook target should read the value of that body, and checkout the correct code accordingly. See also https://docs.pact.io/pact_broker/webhooks#using-webhooks-with-the-contract_requiring_verification_published-event
GitHub
04/10/2025, 9:40 AMSimon Raess
04/17/2025, 9:10 AM