Server hooks (FREE SELF)

Introduced in GitLab 12.8 replacing Custom Hooks.

Server hooks run custom logic on the GitLab server. Users can use them to run Git-related tasks such as:

• Enforcing specific commit policies.
• Performing tasks based on the state of the repository.

Server hooks use pre-receive, post-receive, and update Git server-side hooks.

GitLab administrators configure server hooks on the file system of the GitLab server. If you don't have file system access, alternatives to server hooks include:

• Webhooks.
• GitLab CI/CD.
• Push rules, for a user-configurable Git hook interface.

Geo doesn't replicate server hooks to secondary nodes.

Create server hooks for a repository

To create server hooks for a repository:

1. On the top bar, select Menu > Admin.
2. Go to Overview > Projects and select the project you want to add a server hook to.
3. On the page that appears, locate the value of Gitaly relative path. This path is where server hooks must be located.
   • If you are using hashed storage, see Translate hashed storage paths for information on interpreting the relative path.
   • If you are not using hashed storage:
     • For Omnibus GitLab installations, the path is usually /var/opt/gitlab/git-data/repositories/<group>/<project>.git.
     • For an installation from source, the path is usually /home/git/repositories/<group>/<project>.git.
4. On the file system, create a new directory in the correct location called custom_hooks.
5. In the new custom_hooks directory:
   • To create a single server hook, create a file with a name that matches the hook type. For example, for a pre-receive server hook, the filename should be pre-receive with no extension.
   • To create many server hooks, create a directory for the hooks that matches the hook type. For example, for a pre-receive server hook, the directory name should be pre-receive.d. Put the files for the hook in that directory.
6. Make the server hook files executable and ensure that they are owned by the Git user.
7. Write the code to make the server hook function as expected. Server hooks can be in any programming language. Ensure the shebang at the top reflects the language type. For example, if the script is in Ruby the shebang is probably #!/usr/bin/env ruby.
8. Make the hook file executable, ensure that it's owned by the Git user, and ensure it does not match the backup file pattern (*~).

If the server hook code is properly implemented, it should execute when the Git hook is next triggered.

Create global server hooks for all repositories

To create a Git hook that applies to all repositories, set a global server hook. The default global server hook directory is in the GitLab Shell directory. Any server hook added there applies to all repositories, including:

• Project and group wiki repositories. Their storage directory names are in the format <id>.wiki.git.
• Design management repositories under a project. Their storage directory names are in the format <id>.design.git.

Choose a server hook directory

Before creating a global server hook, you must choose a directory for it. The default global server hook directory:

• For Omnibus GitLab installations is usually /opt/gitlab/embedded/service/gitlab-shell/hooks.
• For an installation from source is usually /home/git/gitlab-shell/hooks.

To use a different directory for global server hooks, set custom_hooks_dir in Gitaly configuration:

• For Omnibus installations, set in gitlab.rb.
• For source installations, the configuration location depends on the GitLab version. For:
  • GitLab 13.0 and earlier, set in gitlab-shell/config.yml.
  • GitLab 13.1 and later, set in gitaly/config.toml under the [hooks] section. However, GitLab honors the custom_hooks_dir value in gitlab-shell/config.yml if the value in gitaly/config.toml is blank or non-existent.

Create the global server hook

To create a global server hook for all repositories:

1. On the GitLab server, go to the configured global server hook directory.
2. In the configured global server hook directory:
   • To create a single server hook, create a file with a name that matches the hook type. For example, for a pre-receive server hook, the filename should be pre-receive with no extension.
   • To create many server hooks, create a directory for the hooks that matches the hook type. For example, for a pre-receive server hook, the directory name should be pre-receive.d. Put the files for the hook in that directory.
3. Inside this new directory, add your server hook. Server hooks can be in any programming language. Ensure the shebang at the top reflects the language type. For example, if the script is in Ruby the shebang is probably #!/usr/bin/env ruby.
4. Make the hook file executable, ensure that it's owned by the Git user, and ensure it does not match the backup file pattern (*~).

If the server hook code is properly implemented, it should execute when the Git hook is next triggered.

Chained server hooks

GitLab can execute server hooks in a chain. GitLab searches for and executes server hooks in the following order:

• Built-in GitLab server hooks. These server hooks are not customizable by users.
• <project>.git/custom_hooks/<hook_name>: Per-project hooks. This location is kept for backwards compatibility.
• <project>.git/custom_hooks/<hook_name>.d/*: Location for per-project hooks.
• <custom_hooks_dir>/<hook_name>.d/*: Location for all executable global hook files except editor backup files.

Within a server hooks directory, hooks:

• Are executed in alphabetical order.
• Stop executing when a hook exits with a non-zero value.

Environment variables available to server hooks

You can pass any environment variable to server hooks, but you should only rely on supported environment variables.

The following GitLab environment variables are supported for all server hooks:

The following Git environment variables are supported for pre-receive and post-receive server hooks:

Custom error messages

You can have custom error messages appear in the GitLab UI when a commit is declined or an error occurs during the Git hook. To display a custom error message, your script must:

• Send the custom error messages to either the script's stdout or stderr.
• Prefix each message with GL-HOOK-ERR: with no characters appearing before the prefix.

For example:

#!/bin/sh
echo "GL-HOOK-ERR: My custom error message.";
exit 1