Integrating with GitLab Community and GitLab Enterprise
You can configure Rational Team Concert process support for push operations through GitLab pre-receive hooks. You can also enable linking between work items and GitLab commits.
Before you begin
About this task
You can define permissions for Push operations based on the role of the user in Rational Team Concert and configure preconditions for Push operations.
To enable linking work items to commits, you configure GitLab post-receive hooks or webhooks, so that after a push operation completes, the registered Rational Team Concert server is notified, and a work item is linked to the commits, based on the comments in the push.
For process support, GitLab and Rational Team Concert should share a user base. For linking work items to Git commits, a shared user base is not mandatory and a Rational Team Concert functional user can be used.
You can capture a commit discussion from GitLab in all the Rational Team Concert work items that are mentioned in the commit comment using GitLab webhooks. By default, the content of the commit discussion, without formatting, is captured in the work items that are referenced in the commit comment. If you disable replication of content in work items, then only a link to the commit discussion is added to the work items mentioned in the commit comment. Attachments are not copied into work items.
You can add a comment in a GitLab issue or commit discussion which references a Rational Team Concert work item and have that comment captured in Rational Team Concert the work item by using GitLab webhooks. By default, the content of the comment is added to the work item without formatting. If you disable replication of content in work items, then only a link to the issue comment or commit discussion comment is added in the work item. Attachments are not copied into work items.