You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
After we issued a new license to our Bitbucket. transitioned from a 'Server' to a 'Data Center' license, all the 'external-pre-receive-hook' executions failed, displaying the following error message: "/<bitbucket_home>/shared/external-hooks/<>: No such file or directory remote: external-pre-receive-hook declined."
Currently, all 'external-hooks' scripts are located at '/<bitbucket_home>/external-hooks/'. However, the server is expecting them to be in '/<bitbucket_home>/shared/external-hooks/'.
Could you please advise on how to direct new scripts to be written to the 'shared/external-hooks' folder or how to direct the server to look for the hooks at 'bitbucket/external-hooks'?
Currently, we've temporarily fixed it by copying the 'external-hooks' folder to the 'shared' configuration. However, a more permanent solution would involve configuring either the script writing process or the server configuration.
The text was updated successfully, but these errors were encountered:
Hello,
After we issued a new license to our Bitbucket. transitioned from a 'Server' to a 'Data Center' license, all the 'external-pre-receive-hook' executions failed, displaying the following error message:
"/<bitbucket_home>/shared/external-hooks/<>: No such file or directory remote: external-pre-receive-hook declined."
Currently, all 'external-hooks' scripts are located at '/<bitbucket_home>/external-hooks/'. However, the server is expecting them to be in '/<bitbucket_home>/shared/external-hooks/'.
Could you please advise on how to direct new scripts to be written to the 'shared/external-hooks' folder or how to direct the server to look for the hooks at 'bitbucket/external-hooks'?
Currently, we've temporarily fixed it by copying the 'external-hooks' folder to the 'shared' configuration. However, a more permanent solution would involve configuring either the script writing process or the server configuration.
The text was updated successfully, but these errors were encountered: