On Thu, 15 Jun 2023 at 03:15, Chad Wilson <[email protected]> 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 affect that pipeline's materials, I > would *guess* that they would end up batched into one pipeline instance > when stage1 next triggers. > That’s correct. They will get batched. The next run will see commits from both those triggers. It’s just a normal material update check to GoCD. Cheers, Aravind > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CACxychGTW%3DdU2LoCTxCgW6tyk16ZzmOhvvX%2BvddHiXs20%2Bw4kA%40mail.gmail.com.
