Skip to Content
Last modified by Boris Folgmann on 2025/12/01 14:53
From version 2.3
edited by Milad Afshar-Jahanshahi
on 2025/11/26 12:40
Change comment: There is no comment for this version
To version 6.1
edited by Milad Afshar-Jahanshahi
on 2025/11/26 12:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,15 +3,15 @@
3 3  The entries do not describe real errors, but rather provide assistance on how to avoid inconsistencies between GitLab and the central user management via the self-service portal.
4 4  
5 5  
6 -(% style="margin-right:auto; width:1345.83px" %)
7 -|=(% style="white-space: nowrap; width: 133px;" %)Title|=(% style="white-space: nowrap; width: 276px;" %)Description|=(% style="white-space: nowrap; width: 349px;" %)Reproduction|=(% style="white-space: nowrap; width: 302px;" %)Recommendation to avoid Errors|=(% style="white-space: nowrap; width: 209px;" %)Workaround in case of Errors|=(% style="white-space: nowrap; width: 74px;" %)Solved
8 -|(% style="width:133px" %)Initial "Migration" of projects to GitLab|(% style="width:276px" %)If GitLab has been added to an existing toolchain, there could be errors if user changes are performed before the project (group) is known in GitLab.|(% style="width:349px" %)(((
6 +(% class="table-bordered" style="margin-right:auto; width:1345.83px" %)
7 +|=(% style="white-space: nowrap; width: 133px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Title|=(% style="white-space: nowrap; width: 271px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Description|=(% style="white-space: nowrap; width: 357px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Reproduction|=(% style="white-space: nowrap; width: 296px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Recommendation to avoid Errors|=(% style="white-space: nowrap; width: 209px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Workaround in case of Errors|=(% style="white-space: nowrap; width: 74px; background-color: rgb(240, 240, 238); border-color: rgb(136, 136, 136);" %)Solved
8 +|(% style="border-color:#888888; width:133px" %)Initial "Migration" of projects to GitLab|(% style="border-color:#888888; width:271px" %)If GitLab has been added to an existing toolchain, there could be errors if user changes are performed before the project (group) is known in GitLab.|(% style="border-color:#888888; width:357px" %)(((
9 9  1. There is already a project before adding GitLab
10 10  1. GitLab is added to the toolchain
11 11  1. Now a user is added to the project or a role of a user in that project is changed
12 12  1. This leads to an error because the project is still not existing in GitLab as a group 
13 -)))|(% style="width:302px" %)"Migrate" existing projects to GitLab right after adding GitLab to the toolchain. For this, force the creation of groups in GitLab by slightly changing the description of each project in the self-service portal. This change will force to create the group in GitLab.|(% style="width:209px" %)Update the project afterwards in the self-service portal. This will fix the missing group needed for a project in GitLab.|(% style="width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
14 -|(% style="width:133px" %)User edit while deassigned from GitLab|(% style="width:276px" %)When a user is deassigned from GitLab and the user name changed afterwards in the self-service portal, then this change is not performed in GitLab.|(% style="width:349px" %)(((
13 +)))|(% style="border-color:#888888; width:296px" %)"Migrate" existing projects to GitLab right after adding GitLab to the toolchain. For this, force the creation of groups in GitLab by slightly changing the description of each project in the self-service portal. This change will force to create the group in GitLab.|(% style="border-color:#888888; width:209px" %)Update the project afterwards in the self-service portal. This will fix the missing group needed for a project in GitLab.|(% style="border-color:#888888; width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
14 +|(% style="border-color:#888888; width:133px" %)User edit while deassigned from GitLab|(% style="border-color:#888888; width:271px" %)When a user is deassigned from GitLab and the user name changed afterwards in the self-service portal, then this change is not performed in GitLab.|(% style="border-color:#888888; width:357px" %)(((
15 15  1. Create a user A, and add tool GitLab to the user
16 16  1. The user account A is created in GitLab
17 17  1. Remove GitLab tool assignment from the user A in the self-service portal
... ... @@ -20,17 +20,17 @@
20 20  1. The result: user account in GitLab is still A
21 21  
22 22  Until a new user name update in the self-service portal the name in GitLab remains the same. Role changes do not affect the user name either.
23 -)))|(% style="width:302px" %)Avoid the change of a user name for a user which was assigned to GitLab and is now deassigned.|(% style="width:209px" %)After reassigning the user to GitLab, change the user name again in the self-service portal, then this changed user name will be propagated to GitLab.|(% style="width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/error.svg||alt="(Fehler)"]]
24 -|(% style="width:133px" %)Technical Users |(% style="width:276px" %)The creation of technical users for Gitlab in the self-service portal is currently not supported.|(% style="width:349px" %) |(% style="width:302px" %)Don't use the technical user feature in the self-service portal for GitLab.|(% style="width:209px" %)Use the features within GitLab to setup tokens for technical users.  |(% style="width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/error.svg||alt="(Fehler)"]]
25 -|(% style="width:133px" %)Comma in Project Names|(% style="width:276px" %)GitLab doesn't like commas in the Group name and rejects corresponding API calls.|(% style="width:349px" %) |(% style="width:302px" %)Project names in the self-service portal must not include commas|(% style="width:209px" %) |(% style="width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
26 -|(% style="width:133px" %)Special characters in Project Names|(% style="width:276px" %)(((
23 +)))|(% style="border-color:#888888; width:296px" %)Avoid the change of a user name for a user which was assigned to GitLab and is now deassigned.|(% style="border-color:#888888; width:209px" %)After reassigning the user to GitLab, change the user name again in the self-service portal, then this changed user name will be propagated to GitLab.|(% style="border-color:#888888; width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/error.svg||alt="(Fehler)"]]
24 +|(% style="border-color:#888888; width:133px" %)Technical Users |(% style="border-color:#888888; width:271px" %)The creation of technical users for Gitlab in the self-service portal is currently not supported.|(% style="border-color:#888888; width:357px" %) |(% style="border-color:#888888; width:296px" %)Don't use the technical user feature in the self-service portal for GitLab.|(% style="border-color:#888888; width:209px" %)Use the features within GitLab to setup tokens for technical users.  |(% style="border-color:#888888; width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/error.svg||alt="(Fehler)"]]
25 +|(% style="border-color:#888888; width:133px" %)Comma in Project Names|(% style="border-color:#888888; width:271px" %)GitLab doesn't like commas in the Group name and rejects corresponding API calls.|(% style="border-color:#888888; width:357px" %) |(% style="border-color:#888888; width:296px" %)Project names in the self-service portal must not include commas|(% style="border-color:#888888; width:209px" %) |(% style="border-color:#888888; width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
26 +|(% style="border-color:#888888; width:133px" %)Special characters in Project Names|(% style="border-color:#888888; width:271px" %)(((
27 27  In GitLab the following characters are allowed in project names:
28 28  
29 29  abcdefghijklmnopqrstuvwxyz ()-_. 0123456789 öäüÖÄÜß ABCDEFGHIJKLMNOPQRSTUVWXYZ
30 -)))|(% style="width:349px" %) |(% style="width:302px" %)(((
30 +)))|(% style="border-color:#888888; width:357px" %) |(% style="border-color:#888888; width:296px" %)(((
31 31  Project names in the self-service portal must consist the following characters only:
32 32  
33 33  abcdefghijklmnopqrstuvwxyz ()-_. 0123456789 öäüÖÄÜß ABCDEFGHIJKLMNOPQRSTUVWXYZ
34 -)))|(% style="width:209px" %)It the Project Name contains other special characters, renaming the Project solves the issues.|(% style="width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
34 +)))|(% style="border-color:#888888; width:209px" %)It the Project Name contains other special characters, renaming the Project solves the issues.|(% style="border-color:#888888; width:74px" %)[[image:https://prd.sdc.t-systems.net/confluence/s/-i01via/9111/1237c1a/_/images/icons/emoticons/check.svg||alt="(Haken)"]]
35 35  
36 36  
© 2018-2025 T-Systems International GmbH