To set up Bitbucket integration you will need to add a webhook for Tickd to your Bitbucket repository and set up a Bitbucket integration in Tickd.
Note that Tickd currently only supports integration with Git repositories hosted in Bitbucket. Mercurial repositories are not supported.
Set up Bitbucket integration in Tickd
You need to set up a name and a URL for your repository in Tickd.
Please Note: If the email address that you use for accessing your Bitbucket repository is different from the email address that you use for logging on to Tickd, add your Bitbucket email address to the list of alternative emails in your user settings.
Add a webhook to your Bitbucket repository
- Go to the home page for your Bitbucket repository on the Bitbucket website.
- Click on the "Settings" menu item in the menu on the left of the page.
- Click the "Webhooks" link at the left of the Settings page.
- Click the "Add Webhook" button on the Webhooks page.
- On the Add new webhook page, enter a value for the webhook title.
- Enter the "Url" value for Tickd. This will be https://<tickd_domain>/rpc/postnote/index.cfm where <tickd_domain> is the domain for your Tickd instance, for example: https://kiltkraft.tickd.it/rpc/postnote/index.cfm
- Make sure that "Active" is selected
- Make sure that the option to "Skip certificate verification" is not selected.
- In the triggers section, select "Push Events"
- Click the Save button to create the Webhook.
To view the integrations that have been set up, click the "Integrations List" icon at the top right of the integrations page. The integrations are listed by name, with an icon showing the integration type. You can filter the list of integrations shown by entering all or part of the integration name in the Filter field at the top left of the page.
- Go to the integrations page for your Bitbucket repository on the Bitbucket site (Repository home page – Settings – Webhooks) The webhooks that have been set up for the repository are listed on the page.
- Click the Edit button for the Tickd webhook to open the webhook page.
- Check that the URL is are correct and that "Repository push" is selected.
- Go back to the webhooks page and click "view requests" to open the request logs page. Click on a recent delivery to view the details.
- The response code for a delivery should be 200. Any response code other than 200 indicates a problem, but some failed deliveries will have a response code of 200, so check the response body which is shown at the bottom of the page. A response of +OK indicates success. If an error message is shown it should give some indication of the issue (See below).
- Response code: 404, Response body: -FAIL: Repository not found – Check that the URLs set for your Tickd integration and your webhook in Bitbucket are correct.
- Response code: 401, Response body: -FAIL: Disabled repository – Check that the Tickd integration is enabled.
- Response code: 200, Response body: -FAIL: No ticket found – Check that the ticket it used in your commit message is correct.
- Response code: 401, Response body: -FAIL: Tickd user not found – Verify that the email associated with your Bitbucket account is the same associated with your Tickd user account, or listed as alternative emails for your Tickd user account