Query :: Can we bypass the pact webhooks and implement CI/CD stage to identify consumer or provider state change to trigger builds

[rakeyshc]

Hello Folks,

My team is implementing contract testing for our microservices. Now we have a scenario to know if we can implement our own custom logic to identify if a contract changes from a consumer side and trigger a CI build to verify the same on the provider side without a webhook.

We are planning to implement this using Gitlab.

Can you please provide some insights on what are the consequences if we dont create a webhook and do a custom change based on either feature branchs or version numbers or tags. I know the matter of fact that if we dont implement a webhook we wont get the benefits of the automation what we usually get automatically from pact.

Some pointer on this can be helpful for us to decide on the approach.

Also what are the benefits we get if we use PactFlow over the broker from a maintaince side of things.

Thanks and Regards,
rakeyshc

[rakeyshc]

Folks

@mefellows
@rholshausen

Any comment from your side can help us gauge further. Apologies for directly tagging you in here.

[rholshausen]

Better to ask this question in the Pact Broker repo. There are APIs in the broker that could help you.

[rakeyshc]

Hi @rholshausen I will do follow this up over there.

Cheers and Thanks
Rakesh

[mefellows]

Yeah, neither of these are related to Pact JVM. I'm going to close the issue for that reason.

We'd be happy to chat further on the above questions in our community workspace (slack.pact.io).

[rakeyshc]

Thanks @mefellows .