You are right in that there has always been the generic material notification api that can be triggered via the post-receive hook. However this API requires a token belonging to an admin user, and in many cases requires physical access to the actual repository.
The webhooks use a different authentication mechanism, which is not tied to an admin user and is much easier to setup (from an admin console in bitbucket, github, ....) Users who are not using one of these hosted options may continue to use the old post-commit hook. On Wed, Feb 21, 2018 at 8:11 AM Darren Rowley <[email protected]> wrote: > I noticed in the release notes for 17.11: > > "Added support for bitbucket webhook." > > But go-cd seems to have always supported notified via the Materials API: > > To notify GoCD via a Git post commit hook, you may use the following post > commit hook in your git repository. > > The post commit hook is located at > /path/to/repository.git/hooks/post-receive. > > > > I'm obviously missing something can someone expand on what the new feature > is and how to use it - there is little documentation? > > > Thanks > > D. > > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
