Hello, Happy New Year! Is there way to link the br...
# pact-broker
é
Hello, Happy New Year! Is there way to link the broker to the pipeline/job that gave publish a result ?
b
I only have small experience with Pact, but I would say yes. You need to have in the pipeline a stage where the Can-I-Deploy runs. You can configure a retry mechanism for the Can-I-Deploy (e.g.: --retry-while-unknown=60 --retry-interval=10) against the broker, to be sure that the results were published in the broker by the provider
👍 1
y
You can set the
buildUrl
when posting verification results, which would store that property to the build Could you clarify a little more on your use case? I have used slack notifications and webhooks to report to a particular CI's build logs for publishing of pacts too
👀 1
@Basu Silviu's method is very good for cases where the consumer publishes a pact which hasn't been verified by the provider. • webhook fires which triggers provider ci build • consumer polls for provider ci result • consumer can deploy if result is successful or fails if no result or failed verification Really neat way for CI/CD
m
Yeah, I read this as “I’d like a link to the build job from the pact broker”.
You can set the
buildUrl
when posting verification results, which would store that property to the build
This is the way to do it, albeit I can’t recall if it’s visible from the UI
é
Yeah, I read this as “I’d like a link to the build job from the pact broker”.
That's what I want, so we can navigate from broker to our gitlab more easily
For reference, one should search for either
buildUrl
but
--build-url
in the docs (e.g. pact_broker-client)
Copy code
[--build-url=BUILD_URL]
              # The build URL that created the pact
b
@Shuying Lin could you add a card somewhere for displaying the build URL in the new UI designs please?
👀 1