Suggested change to PreRepositoryHook

My plugin is reporting findings from the commit messages when commits are pushed. It does not necessarily have to be findings that should reject the commit from being pushed. It can be information, or warnings, that should just be communicated.

If I understand correctly I should, from BBS 6.0, implement this class instead:

If I understand correctly, it can only report feedback with RepositoryHookResult and only when commits are rejected. It cannot report back a text message regarding valid accepted commits.

I would suggest that being changed. That was pretty much the only reason that I started working on this plugin.

A quick googling did not tell my how to make such a request!

1 answer

1 accepted

1 vote
Accepted answer

I haven't ported my own hook to the new BB 6 approach, but from clicking around the javadocs a little, I think you can write messages using the 2nd parameter "T request" of the preUpdate() call.    This "request" param will probably implement RepositoryHookRequest, in which case you can call request.getScmHookDetails().out().

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,963 views 7 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you