On Thu, 15 Jun 2023 at 03:15, Chad Wilson wrote:
> I'm personally not sure if it's 1:1 or not in the case of
> webhook-triggered material updates, but speaking generally I doubt GoCD
> gives this guarantee. e.g if a pipeline's *stage1* is already running,
> and then two webhooks are fired that
I'm not sure I understand the question or what you are trying to achieve,
however.
Webhooks notify the GoCD server of a change to *materials*. The GoCD server
then finds the relevant material(s), and updates them from source to
determine the changes. It then follows normal operations (as it
How do we know the status of the web hook, for example, Say Im firing more
than one web hook to trigger a pipeline, is there a way we can query the
queue status & pipeline instance of the web hook(s) it has picked up?
Second query is above, if we would fire more than one web hook to a same