Hi all, Instead of using Pact-Cli image in my CICD pipeline, I am using an Pact-Cli executable (referring to this link - https://github.com/pact-foundation/pact-ruby-standalone/releases) _"curl -LO https://github.com/pact-foundation/pact-ruby-standalone/releases/download/v2.0.3/pact-2.0.3-linux-x86_64.tar.gz_ _tar xzf pact-2.0.3-linux-x86_64.tar.gz"_ My question here is, after unpacking the tar ball, what are the commands I need to add in my CICD job to use the executable to publish the verified pacts back to pact broker.

This is what I have done so far. Can you tell me where exactly I need to add the path? @Yousaf Nabi (pactflow.io)

https://github.com/pact-foundation/pact-ruby-standalone#package-contents

Binaries will be extracted into `pact/bin`:

Do we need to put these commands in the CICD pipeline? I tired adding it after curl command and before "pact-broker" command in the job.

export PACT_CLI_BIN_PATH=${PWD}/pact/bin/
export PATH=$PACT_CLI_BIN_PATH:${PATH}

the path to the executables are in

pact/bin

once you have downloaded them. therefore the path to the executable can be

pact/bin/pact-broker

from your current working directory.

I am able to download the executable (as seen from the job logs), how can I navigate to pact/bin/pact-broker and use the pact broker command?

you can just do pact/bin/pact-broker publish …

Thank you so much! I am now able to use the pact-cli executable 🙂

great stuff, thx for confirming