Hi@mmanzin

To support BitBucket webhook, you need:

1. add anonymous group at QuickBuild side
2. add BitBucket webhook settings in the configuration setting at QuickBuild side
3. add a webhook at BitBucket side

NOTE: make sure the webhook secret are identical in QuickBuild and BitBucket.

The webhook URL in BitBucket is in following format:

http://{quickbuild.host}/rest/webhook/bitbucket/{configurationId}

Replace the param quickbuild.host and configurationId with your actual value, below is an example I use for testing:

http://demo.pmease.com/rest/webhook/bitbucket/12?target=Android&mode=debug

You don't need any authentication credentials with the URL as we are using the secret defined in webhook settings, but do remember add anonymous group with REST access permission (by default) in QuickBuild.

Hi@steveluo

Thank you for your reply. I had not given REST access to the anonymous group.

Now that everything seems to be set up according to your directions, I am getting a different error: 403, "Invalid signature or secret". I have set up the same secret on both BitBucket and QuickBuild, and I believe it is a valid string. Do you have any idea of what might be causing this problem?

Thank you.

Hi@mmanzin

Normally, this is caused by incorrect encoding of the system. Do you use Windows? Please try add below line to file wrapper.conf which can be located at directory: $quickbuild_installation_dir/conf/

wrapper.java.additional.3=-Dfile.encoding=UTF-8

Please change the number (here is 3) if you have already used this number (3) before.

Hi@steveluo

Thank you for your help, this has been resolved. There seems to be a bug in the "test connection" button when setting up a webhook in BitBucket. If I test the connection from BitBucket, I get a 403 error. However, if I trigger the webhook by doing a commit, then everything works and the build is triggered.

For reference, I am using a Linux machine.

Thank you.