Hello, can anyone help me with my issue: ```2022/0...
# pact-go
m
Hello, can anyone help me with my issue:
Copy code
2022/06/24 11:08:29 [INFO] checking pact-mock-service within range >= 3.5.0, < 4.0.0
2022/06/24 11:08:29 [ERROR] CLI tools are out of date, please upgrade before continuing
FAIL    <http://github.com/pact-foundation/pact-workshop-go/consumer/client|github.com/pact-foundation/pact-workshop-go/consumer/client>     0.002s
When I run "sudo pact-mock-service version" it returns 3.10.0 I am following the https://github.com/pact-foundation/pact-workshop-go/tree/step3 but stuck on the end of step3 and receiving the above issue. Any ideas?
m
is it possible that the version you’ve installed is not on the path that Pact go sees and there as an old version on the path somewhere?
Something like this should put the path of your known correct version as the default
Copy code
export PATH="<add folder containing your version  here>:${PATH}"
then
go test …
m
Hi Matt thanks a lot for this it resolved my issues locally. I am now seeing this when running it in the gitlab runner in my pipeline. Do you know what I would need to export the PATH to be within the pipeline? / Where does the pact binary get installed in a gitlab runner?
🙌 1
m
Hi Matt thanks a lot for this it resolved my issues locally. I am now seeing this when running it in the gitlab runner in my pipeline. Do you know what I would need to export the PATH to be within the pipeline? / Where does the pact binary get installed in a gitlab runner?
If you’re running that bash script, it’s relative to the current working directory. So wherever the default
$PWD
is