nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to configure core.hooksPath for BitbucketServer 4.13

michael_giroux

We currently enforce a standard set of hooks by running a cron job every 10 minutes that creates a symlink to a central hooks directory in any new repository that does not already have the symlink.

Starting with Git 2.9, it is now possible to configure core.hooksPath to specify a central hooks directory common to all repos. This seems a better approach as it is more obvious, and is in effect the moment a new repo is created.

Q1.

To leverage core.hooksPath in Bitbucket Server, I'm guessing that we would set the configuration in the ~/.gitconfig for the user running Bitbucket Server. Is this correct?

Q2.

Do hooks in a repository .git/hooks directory take precedence over hooks in the core.hooksPath location? If not, once core.hooksPath is set, how does one override the global hooks for a specific repository?

Accepted answers

All comments

Stefan F_

hi michael!

i'm experiencing the same issue on my workstation using git 2.16.1 and atlassian sdk with bitbucket 5.7.0.

when i'm starting the bitbucket server testing my hook plugin, the hook is not called, I get an error message

[INFO] 2018-02-06 10:46:26,858 WARN [http-nio-7990-exec-9] admin @1YO4D3Dx646x34x0 127.0.0.1 "POST /scm/project_1/rep_1.git/git-receive-pack HTTP/1.1" c.a.s.i.s.g.p.http.HttpReceivePack PROJECT_1/rep_1[1]: Git hooks have not been called. Please verify that the hooks are configured correctly - see https://confluence.atlassian.com/display/BITBUCKETSERVERKB/Git+hook+scripts+are+not+executing?utm_campaign=in-app-help&utm_medium=in-app-help&utm_source=stash for details

my hookspath is:

core.hookspath=/usr/lib/git-besi/hooks

do you have already contacted atlassian for this issue?

Michael Heemskerk

You should not configure core.hooksPath, nor replace the pre-receive or post-receive hooks in the repository directory; Bitbucket Server relies on these for executing core processes.

Configuring `core.hooksPath` will override the default hooks that Bitbucket Server specifies. As a result, the built-in hooks that verify branch permissions, update pull requests, etc will no longer work.

Hooks that use the RepositoryHook API can be enabled on a per-project or per-repository level through the Project Settings or Repository Settings pages. If you have a RepositoryHook that you want to run on all repositories, you can configure your hook to be non-configurable. See the hooks and merge checks guide for more information.

If you have a hook script that you need to run, you can add it to the hooks/pre-receive.d or hooks/post-receive.d directory of the repository that you want the hook to apply to.

Stefan F_

Hi Michael!

We have one pre-commit hook globally configured for the whole workstation in a path /usr/lib/..../hooks. There is exactly on hook "pre-commit" in there, no pre-receive, etc.

Now, Bitbucket SDK invokes git in the repository path (e.g. /home/blabla/myhook/target/bitbucket/home/shared/data/repositories/1) and does not use the local hook directory?

It would not be a problem setting the local git repository hookspath to this one before invoking git, wouldn't it?

Thanks for the answer!

Michael Heemskerk

If I understand correctly, you're developing a Bitbucket Server plugin on your local machine and have a core.hookspath configured in your ~/.gitconfig. And when you run Bitbucket Server locally (though the SDK), hooks in the Bitbucket repositories are no longer being called?

There are a couple of ways to 'fix' that:

remove the core.hooksPath option from your ~/.gitconfig
start Bitbucket Server as a different user that does not have this global setting configured
add a 'hooksPath = .' setting to the [core] section in BITBUCKET_HOME/shared/config/git/system-config to override the global setting at the Bitbucket level

Hope that helps!

unknown

Based on the comments here, it seems to me that a site should be able to use core.hooksPath without disturbing the basic Stash functionality. But given that it overrides the repository hooks, it seems that some guidelines are required.

all hooks must be implemented in the hooksPath, even ones you do not wish to override or provide logic for.
every hook must delegate to the repository hook to invoke the Bitbucket built-in hooks.

In this way, the site can implement site-wide hooks in hooksPath and retain the full functionality of the repository level hooks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

hook