We have run into a bug using the File Hook plugin, when creating branches locally and trying to push them to the Bitbucket server.
At the time of the push, the local UI shows the following error:
$ git push origin test-branch
Total 0 (delta 0), reused 0 (delta 0)
remote: Communication breakdown with Bitbucket.
To https://xxx/scm/dl/test.git
! [remote rejected] test-branch -> test-branch (pre-receive hook declined)
error: failed to push some refs to 'https://xxx@xxx/scm/dl/test.git'
The server logs show the following error (stacktrace severely trimmed to due Atlassian posting rules):
com.atlassian.stash.internal.plugin.legacy.CompositeRepositoryHook.preUpdate (org.christiangalsterer.stash-filehooks-plugin:filename-hook)
com.atlassian.bitbucket.commit.NoSuchCommitException: Commit '0000000000000000000000000000000000000000' does not exist in repository 'test'.
at com.atlassian.bitbucket.scm.git.command.GitCommandExitHandler.newNoSuchCommitException(GitCommandExitHandler.java:167)
Disabling the File Hooks plugin enables us to push the new branches but this is of course not ideal.
We are running Bitbucket 5.0.4 (with plans to upgrade to latest soon) and File Hooks plugin 3.0.0.
Anyone aware of plans to fix this issue?
Regards,
Nicolas
