Make sure there is a codeBeamer user with the same username as the pusher in GitLab or use the pusher email (
see below)
Make sure there is no repository in the project with the same name
There are 2 things to do in codeBeamer:
- Create user(s) who has the same username as the pusher(s) in GitLab.
- Add the secret token of the webhook to codeBeamer configuration (see below)
Steps to configure secret token in codeBeamer:
- Go to codeBeamer's System Admin page
- Go to Application Configuration
- Add "scc" node if it is not exist in your json (json root level)
- Add "gitlab" node if it is not exist in your json under "scc" node
- Add "secretToken" : "<secret_token_of_the_webhook>" under "gitlab" node
Example:
Steps to configure GitLab webhook:
- Navigate to the Settings page of a repository
- Choose the Integrations menu
- Fill out the fields
- URL: <codebeamer_url>/rest/scm/gitlab/<project_id>
Where codebeamer_url is the url of your codeBeamer and project_id is the id of your project where the GitLab repository will belong to after the first webhook execution
Example: https://codebeamer.com/cb/rest/scm/gitlab/1
- Secret Token: codeBeamer validates the source of the requests with the Secret Token. It is required to set the same Secret Token in GitLab and in codeBeamers's Application Configuration too (see above)
- Select "Push events" (codeBeamer supports only push event)
- Check/Uncheck Enable SSL verification according to your codeBeamer server SSL configuration
- Click Add webhook
This feature is available since codeBeamer 9.5
In case there is no user in codeBeamer with the same username as the pusher in GitLab codeBeamer will use the user for repository operations who has the same email address as the pusher.
Set the correct email address:
- Go to Settings --> Profile --> Main settings --> Public email
- Select your email address instead of 'Do not show on profile' then Click update profile settings