hey all, someone already face this error before:

Pact contract publishing failed:  Error: Pact publication failed with non-zero exit code. Full output was:
<internal:gem_prelude>:4:in `require': cannot load such file -- rubygems.rb (LoadError)
        from <internal:gem_prelude>:4:in `<internal:gem_prelude>'

what i did: • created a

publish.js

• run the

publish.js

to publish the pacts into pactflow

You're running onto the notorious windows long path issue. You'll need to move closer to C:

so basically i have this options:

pact-broker publish pacts/ --consumer-app-version 1.0.0 --branch main --broker-base-url=<URL> --broker-token=<TOKEN>

to use this i need to install the

pact-broker

?

Yes. Or you can continue to use it as is, but just move the working directly closer to

c:\

. There is a 255 character limit in path names, and you’re chewing up a bunch there 😉

thanks @Matt (pactflow.io / pact-js / pact-go) but i don't think is a good approach, because the

publish.js

point to pacts folder right? so the pactFilesOrDirs will be long as well... for example, my plan is to run locally and also at github actions and to do it manage the path will be kind confusing to other members of my team! i didn't find an option to use pact-broker in the docs, i mean, there is no setup to use it...

but i don’t think is a good approach, because the

publish.js

point to pacts folder right? so the pactFilesOrDirs will be long as well...

it’s not the file path of the pacts to publish, it’s actually an underlying Ruby library that exceeds the length.

right @Matt (pactflow.io / pact-js / pact-go) yes i was kind confusing, but i have more understanding right now! Anyway I managed to publish the pacts and I'm getting the passed result when i run the Pact Verification step provider file:

import { Verifier } from '@pact-foundation/pact';

describe('Pact Verification', () => {
  jest.setTimeout(50000);
  test('validates the expectations of Matching Service', () => {
    return new Verifier({
      providerBaseUrl:
        'providerBaseUrl',
      publishVerificationResult: true,
      providerVersion: '2.0.0',
    })
      .verifyProvider()
      .then((output) => {
        console.log('Pact Verification Complete!');
        console.log(output);
      });
  });
});

result

@Gustavo Souza no….

also the result at pactflow

that result is “unverified” - this means the verification either didn’t run properly, didn’t publish or both

about the “not verified” result I really don't know, maybe it's related to not being able to perform provider verification

There are two types of publishing: 1. Publishing your pact files (the contract) 2. Publishing the verification results (the provider has verified one or more contracts, and the results are published back to a Pact Broker)