[SOLVED] Gitlab VCS cannot pull Orgnaizations/Groups projects

So i was testing the VCS (already made another issue regarding the UI https://discord.com/channels/564160730845151244/1551883517502300160 ) but i found another issue, and this time, in the API side.

Basicly my gitlab user is "ibaraki" but my appwrite projects are on "appwrite/".

This cause an issue as the VCS handler tries to map the username instead of the group name on the project :

$owner = $vcs->getOwnerName($providerInstallationId); // no repo id

where the fix is apparently : in a Get.php file :

$owner = $vcs->getOwnerName($providerInstallationId, (int) $providerRepositoryId);

Also this happen for : gitlab.com | gitlab self-hosted | gitea

there might be another issue as the build logs says "Download failed with status 404", i'm looking into that

apparently same issue tho somewhere else in the API for the build worker process

so part one is in file : src/Appwrite/Platform/Modules/VCS/Http/Installations/Repositories/Get.php
and part two is in : src/Appwrite/Platform/Modules/Compute/Base.php

oh there is more than just two paths in the API ...

bue it's the same root cause, just spread kinda everywhere in the VCS feature + worker builds

YEY it works now

• All patched files (based on 2.2.0, you can use the github source and diff the files from the 2.2.0 tag) : https://gitlab.ibaraki.app/helm/appwrite/-/tree/bde3dfe1b93f545f26140c31b2881f3c00132690/charts/appwrite/files
• Build worker file path : https://gitlab.ibaraki.app/helm/appwrite/-/blob/bde3dfe1b93f545f26140c31b2881f3c00132690/charts/appwrite/templates/workers.yaml#L197-200
• API files paths : https://gitlab.ibaraki.app/helm/appwrite/-/blob/bde3dfe1b93f545f26140c31b2881f3c00132690/charts/appwrite/templates/appwrite-api.yaml#L67-88

[SOLVED] Gitlab VCS cannot pull Orgnaizations/Groups projects

Not released yet, tho next release, it's good