Hi folks! I am trying to learn more about Pactflow...
# pactflow
j
Hi folks! I am trying to learn more about Pactflow, and am going through the CI/CD workshop in Pactflow university, but am getting stuck at the section of "how to break everything." .... I can't break everything! I have my consumer set up so that it expects an extra field that my provider does not provide, and I have run my consumer tests and published my pact to Pactflow. This triggers the provider workflow verify-changed-pact, via webhook which fails as expected. However, when I run the provider build workflow manually as described in the "Run the provider build" section, the build passes just fine, which I wasn't expecting based on the next page, which has me switch the enablePending flag to true. Am I misunderstanding when things should fail? Thanks!
b
what are the selectors configured in the provider tests @Jon?
and what is the branch or tag name of your broken pact?
j
For selectors I've been cycling between
_consumerVersionSelectors_: [{ _tag_: 'master', _latest_: true }, { _deployed_: true } ], _// the new way of specifying which pacts to verify_
and
//consumerVersionSelectors: [{ tag: 'master', latest: true } ]
and my branch is "master" for both consumer and provider
b
they should both work, because you've got the master pact in there both times.
when you run the verification, what is the output? you should see the URL of the pact being verified.
when you follow that link, is it the pact that has the new expectation in it?
j
I did notice the version used for verification corresponded to the SHA from my commit associated with the consumer that was not expecting an extra field
b
double check that the pact in the broker with the latest master tag is the one you think it is
j
okay, it looks like it is
b
can you show me the tag info?
j
this info?
b
yup. just show me the tag please.
check on the overview page
want me to have a look for you?
j
ah sorry, here you go:
b
@Jon if you dm me your tenant, and I'll log in and have a look for you.
👍 1