From a693539ff998cf3d1cfd43282ef22ad461fa5a65 Mon Sep 17 00:00:00 2001 From: Valentine Burley Date: Tue, 19 Aug 2025 09:55:28 +0200 Subject: [PATCH] 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 Part-of: --- .gitlab-ci/setup-test-env.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitlab-ci/setup-test-env.sh b/.gitlab-ci/setup-test-env.sh index 21a152333e0..9a6312cb11d 100755 --- a/.gitlab-ci/setup-test-env.sh +++ b/.gitlab-ci/setup-test-env.sh @@ -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}"