External Hooks by Reconquest

Very prompt response on support request. Relatively minor issue but support team were able to point me in the direction of a version that worked for us.

• 

  Reconquest

  Thanks!

Hi Team, I have configured a external hooks plugin for the purpose of pre-receive hook , it has to reject the push if Jira keys are not valid . I have shell script and kept into bitbucket server and mentioned the path in the "Executable" section in the plugin . But my hook is not working even its not calling the hook . Example : /opt/bitbucket/hooks/pre-receive.sh The same script i have tested in the bare repository its working fine . /opt/bitbucket/home/shared/data/repositories/82/hooks/pre-receive I'm felt that configuration was not correct , but don't know how to configure , could you please share me the configuration of the plugin so that I will follow the same . What I have done is : Copied the script to stash server in the path : /opt/bitbucket/hooks/pre-receive.sh Went to the repository setting--> hooks--> External Pre receive Hooks --> Executable --> /opt/bitbucket/hooks/pre-receive.sh --> Save Then Cloned a repo switched to branch apply changes commit it push Its not calling the hook script .

• 

  Reconquest

  Hello, Ashok G

  Could you please let us know which version of BB and External Hooks are you running?

  Please send the response to our support email: we@reconquest.io

  We'll be glad to help you because the scenario that you're describing is expected to be working.

This is great! We are a Python-centric dev shop and this allows me to write hooks in the language I know best.

This plugin used to work great for us with Stash 3.11.1 and Git 1.9.5 We just upgraded to BitBucket 5.1.0 with Git 2.12.1 and the plugin stopped working. Took me a while to identify, what I think is maybe a problem. Git 2.11 "significant changes to push handling on the server" (ref. https://github.com/sford/yet-another-commit-checker/issues/139), more specifically "...The new quarantining behavior that was added for pushes creates a random temporary directory where the newly-received objects are written, and exports GIT_OBJECT_DIRECTORY , GIT_ALTERNATE_OBJECT_DIRECTORIES and GIT_QUARANTINE_PATH ..." Our custom pre-receive hook uses 'ls-tree' to examine the ${newrev} commit for improperly named files and folders, which would violate our directory structure policy. Now we're getting an error that it is not a tree object. Similarly, 'cat-file' errors out with "could not get object info", 'log' says "bad object" and diff says "invalid range". It all boils down to git not being able to see the ${newrev} object that the plugin passes to the script. I was trying to find a place to submit this bug report, but didn't find any links on the project's GitHub page. For now, it looks like we'd have to disable this hook, unfortunately :(