Hi All, Looking at the webhook dynamic variable: `...
# pactflow
n
Hi All, Looking at the webhook dynamic variable:
${pactbroker.buildUrl}
The URL of the build that published the resources that have triggered the webhook (currently only supported for contracts published using the ‘all in one’ endpoint). What does “currently only supported for contracts published using the ‘all in one’ endpoint” relate to?
I’m publishing my pacts setting the
pact.publish.consumer.buildUrl
And my assumption was that when the webhook gets triggered it would be sent with the
"${pactbroker.buildUrl}"
dynamic variable
m
That's a fair point and a confusing message. It just means that the pact publish must use a particular (a newer) API. If you're using the CLI it will, and I think most modern JVM versions do too. You'll find out pretty quick if yours doesn't support it
That API has been out for a while, but I'll follow up
n
Hey Matt, Using the latest gradle plugin and not seeing the buildUrl come through on the webhook. I can try publishing the pacts with the CLI to see if that makes a difference.
👍 1
(It’s referenced in the gradle task if I read the code correctly)
n
Thanks! I think I’m being an idiot and mistake in implementation. Will confirm
😆 1
Can confirm being an idiot!
😆 1
It does what I expected it to do
m
We all get one free pass 🤣
n
I feel like I ran out of those a while back!