是否可以在 gitlab 8 中使用自定义挂钩进行项目提交？
Is it possible to use custom hooks in gitlab 8 for project commit?
我知道无法将 custom_hooks 应用于项目提交。
现在可以用 gitlab 8 吗？
谢谢。
Here 是描述如何操作的完整文档。
Note: Custom git hooks must be configured on the filesystem of the GitLab server.
Only GitLab server administrators will be able to complete these tasks. Please explore webhooks as an option if you do not have filesystem access.
For a user configurable Git Hooks interface, please see GitLab Enterprise Edition Git Hooks.
Git 原生支持在不同操作上执行的挂钩。服务器端 git 挂钩的示例包括预接收、post-接收和更新。有关每种挂钩类型的详细信息，请参阅 Git SCM 服务器端挂钩。
从 gitlab-shell 版本 2.2.0（需要 GitLab 7.5+）开始，Git实验室管理员可以添加自定义 git 挂钩到任何 Git 实验室项目。
设置
Normally, git hooks are placed in the repository or project's hooks directory. GitLab creates a symlink from each project's hooks directory to the gitlab-shell hooks directory for ease of maintenance between gitlab-shell upgrades. As such, custom hooks are implemented a little differently. Behavior is exactly the same once the hook is created, though. Follow these steps to set up a custom hook.
- Pick a project that needs a custom git hook.
On the GitLab server, navigate to the project's repository directory. For an installation from source the path is usually /home/git/repositories/<group>/<project>.git.
For Omnibus installs the path is usually
/var/opt/gitlab/git-data/repositories/<group>/<project>.git.
Create a new directory in this location called custom_hooks.
Inside the new custom_hooks directory, create a file with a name matching the hook type. For a pre-receive hook the file name should be pre-receive with no extension.
Make the hook file executable and make sure it's owned by git.
- Write the code to make the git hook function as expected. Hooks can be in any language. Ensure the 'shebang' at the top properly reflects the language type. For example, if the script is in Ruby the shebang will probably be
#!/usr/bin/env ruby.
就是这样！假设挂钩代码已正确实现，挂钩将在适当时触发。
我知道无法将 custom_hooks 应用于项目提交。
现在可以用 gitlab 8 吗？
谢谢。
Here 是描述如何操作的完整文档。
Note: Custom git hooks must be configured on the filesystem of the GitLab server.
Only GitLab server administrators will be able to complete these tasks. Please explore webhooks as an option if you do not have filesystem access.
For a user configurable Git Hooks interface, please see GitLab Enterprise Edition Git Hooks.
Git 原生支持在不同操作上执行的挂钩。服务器端 git 挂钩的示例包括预接收、post-接收和更新。有关每种挂钩类型的详细信息，请参阅 Git SCM 服务器端挂钩。
从 gitlab-shell 版本 2.2.0（需要 GitLab 7.5+）开始，Git实验室管理员可以添加自定义 git 挂钩到任何 Git 实验室项目。
设置
Normally, git hooks are placed in the repository or project's hooks directory. GitLab creates a symlink from each project's hooks directory to the gitlab-shell hooks directory for ease of maintenance between gitlab-shell upgrades. As such, custom hooks are implemented a little differently. Behavior is exactly the same once the hook is created, though. Follow these steps to set up a custom hook.
- Pick a project that needs a custom git hook.
On the GitLab server, navigate to the project's repository directory. For an installation from source the path is usually
/home/git/repositories/<group>/<project>.git. For Omnibus installs the path is usually/var/opt/gitlab/git-data/repositories/<group>/<project>.git.Create a new directory in this location called custom_hooks.
Inside the new custom_hooks directory, create a file with a name matching the hook type. For a pre-receive hook the file name should be pre-receive with no extension.
Make the hook file executable and make sure it's owned by git.
- Write the code to make the git hook function as expected. Hooks can be in any language. Ensure the 'shebang' at the top properly reflects the language type. For example, if the script is in Ruby the shebang will probably be
#!/usr/bin/env ruby.
就是这样！假设挂钩代码已正确实现，挂钩将在适当时触发。