To set up GitLab integration you will need to add a webhook for Tickd to your GitLab repository and set up a GitLab integration in Tickd.
Set up GitLab integration in Tickd
You need to let Tickd know a logical name, a URL of your repository in GitLab and the secret value.
Please Note: If the email address that you use for accessing your GitLab repository is different from the email address that you use for logging on to Tickd, add your GitLab email address to the list of alternative emails in your user settings.
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.
Add a webhook to your GitLab repository
- Go to the home page for your GitLab repository on the GitLab website.
- Click on the "Settings" menu item in the menu on the left of the page.
- Under the "Settings" menu item, click "Integrations"
- 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
- Optionally, set a value in the "Secret" field
- Make sure "Push Events" is selected
- "SSL Verification" should be enabled
- Click the "Add Webhook" button to create the Webhook.
- Go to the integrations page for your GitLab repository on the GitLab site (Repository home page – Settings – Integrations) 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 and Secret Token (if set) are correct and that "Push Events" are selected.
- Recent deliveries are listed at the bottom of the 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 GitLab are correct.
- Response code: 401, Response body: -FAIL: Invalid secret –Verify that the Secret value set in the webhook and Tickd integration are identical.
- 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 GitLab account is the same associated with your Tickd user account, or listed as alternative emails for your Tickd user account