Hi again guys, What am I missing here? I have recorded a deployment of a provider -

Recorded deployment of core-api version bb6600cd to production environment in the Pact Broker.

I have have pushed the pact between

caller-identities

consumer and this provider

Pact successfully published for caller-identities version 8dc3a26e and provider core-api.

Which triggered a verification - which passed. I can see in the pact-broker that the pacts were verified (attached image) And yet

can-i-deploy

returns false -

There is no verified pact between version 8dc3a26e of caller-identities and the version of core-api currently in production (bb6600cd)

Any help will be appreciated

The provider version in the screenshot (the one that has verified the pact) is

bb6600c

but you recorded deployment of version

bb6600cd

- is that a typo or the mistake?

It's not a typo, it just doesn't show the full version. I am using Gitlab's

CI_COMMIT_SHORT_SHA

as version.

So is the issue the same, except rather than the SHA being shorter, it’s much longer? Are you using the same sha to tag the provider on verification results and can-i-deploy?

I am not passing anything manually, I am using the same Gitlab

${CI_COMMIT_SHORT_SHA}

yes, they are the same

And you are correct 🙂