The documentation talks about how to create one's own repository hooks but does not mention how to enable it. The UI only search for market place ones when I click on "Add Hooks". So the question is: what's the real flow of adding one's own hooks?
Deshuang -
You would place your hook scripts in the "hooks" directory for your repository. If you have SVN, it would looks something like:
/SVN
/Repository-Name
/hooks
There you can add your pre or post commit hooks. For example there is a pre-commit hook that is available in the market place that allows you to restrict commits to your repository if there is not a valid JIRA ticket number in the comments section. You would place the hook files (modified for your environment) into that /hooks directory and bounce your repository server.
There may be some dependencies that you have to install depending on what your hook script is written in i.e. perl or python.
Your script would do something like invoke the REST API to access JIRA, log in, and validate that the comment section of the commit contains a valid JIRA ticket number that is in "Open" status or whatever you need to verify.
Hope that helps some....
-Ed
Thanks for answering and that works. I also want to add a plugin so it shows in UI as well. Adam Ahmed has answered that part.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Writing your own hook involves creating one of those plugins and uploading it to your server through the Stash administration.
Our developers docs go through how to create a repository hook plugin: https://developer.atlassian.com/stash/docs/latest/how-tos/repository-hooks.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your answer. The document is very useful. But where do I add that plug in to the server. I saw it only talks about testing it using another server within the SDK? Thanks, -Deshuang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.