Good afternoon! We have configured the SDLC 1.4 integration following the instructions at Интеграция с Git | SimpleOne Documentation.
The connection has been successfully established.
In the GitLab project, we performed the following steps:
To display entities from GitLab on the Developer Panel, perform the following steps:
- Copy the task number you are working on from the record form or project board into SimpleOne. For example: STR0000001.
- In Git, create a new branch using the task number:
git checkout -b STR0000001-<name-continuation>.
- When committing your changes for the task, include the task number in the commit message:
git commit -m "STR0000001 <commit summary>". For commits to appear on the panel, they must be associated with a branch whose name includes the task number.
- Once all necessary changes have been made to the task branch, create a merge request (MR) to the project’s target branch. Use the SimpleOne task number in the MR title or description.
However, information about branches and merge requests is not appearing on the Developer Panel tab.
In the logs, the following error appears:
Results of connection to portfolio for task STSK0000079 repositories: connection failed for requests
What could be the cause? Which groups should the user be added to? Must GitLab users be identical? What is the purpose of the roles described here? Группы Git | SimpleOne Documentation
Hello!
This log should contain information about specific failed requests, for example, Results of connection to portfolio for task STSK0000079 repositories: connection failed for requests https://gitlab.com/api/v4/projects/XXX/merge_requests/?scope=all&search=STSK0000079&in=title, https://gitlab.com/api/v4/projects/XXX/merge_requests/?scope=all&search=STSK0000079&in=description, .... Which requests are indicated in your logs?
This log appears only when the GitLab server returns a response code other than 200 for one of the requests to a specific repository.
If the connection attached to the project is successful, it means your instance does not block requests to GitLab, and the token is also correct; otherwise, the connection would not have been established. Are there any other repositories besides "portfolio"? Are requests failing there as well? First, you need to determine whether this issue affects all repositories, and then analyze the response codes for these requests (additional logs may need to be enabled).
Typically, connection setup uses a service user account with all necessary permissions. All requests to retrieve information about commits, branches, and MRs are sent using this user’s token. The current user viewing information on the Developer Panel widget does not affect access to Git. Please verify that the read_api option was enabled in GitLab when creating the access token for the connection.
The role descriptions for the "Git Groups" table provide information only about access to viewing groups on your instance; these access rights are not related to GitLab permissions for the specified roles.
Queries in logs: Results of connection to portfolio for task STSK0000079 repositories: connection failed for requests
https://gitlab.com/api/v4/projects/67527831/merge_requests/?scope=all&search=STSK0000079&in=title, https://gitlab.com/api/v4/projects/67527831/merge_requests/?scope=all&search=STSK0000079&in=description,
Further, posting links is prohibited for new users
Other repositories exist but are private; we want to grant access only to the portfolio
We would like to configure a connection to at least one repository to demonstrate the functionality
The token was issued in the profile:
- User Settings
- Access tokens
api, read_api, read_user, create_runner, manage_runner, k8s_proxy, self_rotate, read_repository, write_repository, read_registry, write_registry, ai_features
What needs to be done to identify the issue? What advanced logs are available?
I solved the problem. When selecting a repository, you must select and then save the settings, as filters are not automatically saved. + In GitLab, you must use groups, and the token should be issued for the profile.
Great that you managed to resolve the issue!
Where should the settings be saved? In the SDLC project?
Previously, was your token assigned to a group?
Settings must be saved in the SDLC project—it is not obvious in the interface or in the user manual, and even the YouTube video does not show filter saving: https://rutube.ru/video/70311a946edf98eb021f217559f87a19/
Go to the repository, click “Select All,” exit, and then click “Save.”
The token was on the profile but not in the GIT group.
I created a group and cloned the GIT project into it.