pre-receive hook

[arnabbanerjee]

We have created a pre receive hook plugin for bitbucket server (roughly following the video tutorial https://developer.atlassian.com/blog/2015/01/beer-o-clock-stash-plugin-tutorial/) and the onReceive logic works perfectly for any push that's done from a git client (e.g. through manual "git push" command from CLI).

However, the hook is not getting triggered for any commit that's being done from the bit bucket GUI using the "Edit" feature.

We are using Bitbucket 5.5.1 DC edition.

[Michael Heemskerk]

Hi,

In Bitbucket 5.0, we've introduced a new repository hooks API that allows you to intercept all changes to branches and tags using a unified API. The beer-o-clock blog post is still using the old, now deprecated, API, which does not support intercepting in-browser edits.

Fortunately, the new API does support it. You can find an extensive guide in our developer documentation.

For your use case, you should probably implement `PreRepositoryHook<RepositoryHookRequest>` and check the trigger on the request to determine whether you want to apply your hook's restrictions:

public class ExampleHook implements PreRepositoryHook<RepositoryHookRequest> {
  @Nonnull
  @Override
  public RepositoryHookResult preUpdate(@Nonnull PreRepositoryHookContext context,
                                        @Nonnull RepositoryHookRequest request) {
    if (!shouldIntercept(request.getTrigger()) {
      return RepositoryHookResult.accepted();
    }

    // apply your hook logic here and return accepted() or rejected()

  }

  private boolean shouldIntercept(RepositoryHookTrigger trigger) {
     // customize to include all triggers the hook should respond too
     return trigger == StandardRepositoryHookTrigger.PUSH ||
         trigger == StandardRepositoryHookTrigger.FILE_EDIT;
  }
}