ci: Temporarily hardcode S3 artifact path

GitLab 18.2.2 introduced a security restriction that only allows
uploading artifacts to the user's own namespace.
To work around this, hardcode the artifact location to the path where
the artifacts were uploaded to in
ce0d4f998d ("ci: Fix for GitLab 18.2.2 upgrade").

This is an ugly but temporary workaround until a proper solution is in
place.

Signed-off-by: Valentine Burley <valentine.burley@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/36836>
This commit is contained in:
Valentine Burley 2025-08-19 09:55:28 +02:00 committed by Marge Bot
parent d4586224fb
commit a693539ff9

View file

@ -300,7 +300,7 @@ function find_s3_project_artifact() {
x_off
local artifact_path="$1"
for project in "${FDO_UPSTREAM_REPO}" "${S3_PROJECT_PATH}"; do
for project in "gallo/mesa" "${S3_PROJECT_PATH}"; do
local full_path="${FDO_HTTP_CACHE_URI:-}${S3_BASE_PATH}/${project}/${artifact_path}"
if curl-with-retry -s --head "https://${full_path}" >/dev/null; then
echo "https://${full_path}"