GitLab

After the 25.3.9 release, the structure of the webhook payload URL was updated. Customers need to update the webhook URL in the repository settings of their remote repo. Some customers are still using the old webhook URL containing autorabitrest, which should now be replaced with api.

Example:

Old URL: https://na25.autorabit.com/autorabitrest/webhook/triggerSCMPushrequest

Updated URL: https://na25.autorabit.com/api/webhook/v2/<OrgName>/trigger-scm-push-request

Unless you update the Payload URL, you might face pull request/trigger build-on-commit jobs triggering.

A. Create a Webhook API Token from ARM

1. Log in to ARM.

2. Navigate to Admin > API Token.

3. Click Create API Token.

1. Enter a Token Name.

2. Select Type as webhook.

3. (Optional) Add a Description.

4. Click Create Option.

1. Your API token is now created.

B. Create a Webhook with Authentication on GitLab

1. Log in to your GitLab account and select the target repository.

1. Go to Settings > Integrations.

1. In the URL field, enter the webhook endpoint:

For example: https://login.autorabit.com/api/webhook/v2/autorabit.com/trigger-scm-push-request

1. Complete the configuration and click Add Webhook.

Smart Commits

Define the pattern used to extract ALM-related information from commit messages. For example:

To enable automatic updates via webhook:

• Check the Enable auto update on webhook option.

• This will display the required webhook URL for use in repository settings.

For more detailed setup across repositories, refer to the Webhook Configuration Guide. To integrate with external Smart Commit systems, see the Version Control Repositories Summary.

For Enterprise Customers

Use the following endpoints for enterprise-specific configurations: /api/webhook/v2//enterprise/trigger-scm-push-request /api/webhook/v2//enterprise/sync-alm-commits